| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
This reverts commit 74e65cbf111a4f17fa393192519910de53d6c7ac.
|
| |
|
|
| |
This reverts commit c69b38827091b64c7091e415c6596a7045fd5039.
|
| |
|
|
| |
This reverts commit 8a4fdd59c1d0d613cb32778b7142da8ec0adbab1.
|
| |
|
|
| |
This reverts commit a24e722ebcb06c88f88605190caebdcf83236690.
|
| | |
|
| |
|
|
|
|
| |
Sometimes we need to compare serials, and sometimes we need to display
them. The two aren't necessarily the same thing, so add a function to
differentiate them.
|
| |
|
|
|
|
| |
We're not internally determining multipaths any more, so we don't
really need a separate infrastructure for device serial numbers. Also,
add a generic DMDevice.serial that gets it from self.dmUuid
|
| |
|
|
|
| |
If we don't have a multipath.conf when we scan, we get a default blacklist
of everything, which isn't helpful. So write one.
|
| | |
|
| |
|
|
|
| |
Remember that this step does not exist in text mode and we therefore cannot
add it back into the step list when autopart fails.
|
| | |
|
| |
|
|
| |
Reimplement the old isys.getDasdPorts() function in Python.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PartitionDevice was inheriting the currentSize property from StorageDevice,
but that uses partedDevice.getSize() which returns 1024 when called on
extended partitions (as that is what the kernel reports).
This causes _setTargetSize() to try and change the extended partition geometry
even when called with the current extended partition geometry size, as
currentSize was mis-reporting the extended partition size. Since
we do end sector alignment now a days when changing the partition geometry,
we could end up making the extended partition to small to hold the
last logical partition resulting in a:
PartitionException: Unable to satisfy all constraints on the partition.
Error. This patch fixes this by adding a currentSize method to the
PartitionDevice class, which properly reports the currentSize for extended
partitions.
|
| |
|
|
|
| |
Otherwise, we traceback trying to mount /mnt/sysimage/None or something
stupid like that.
|
| | |
|
| | |
|
| |
|
|
| |
xfs_admin expects -L <label> <device>.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds a warning when ignoring BIOS RAID members because no complete
set using them could be found.
This patch also introduces a much needed InstallInterfaceBase class, as I
didn't feel like adding the exact same code to all of cmdline.py, gui.py and
text.py .
Note that the ignoring of BIOS RAID members is checked in 2 places, as
the filter UI can be skipped under certain circumstances (kickstart). The
interface code checks for disks it has already warned about.
|
| |
|
|
|
|
| |
Due to recent changes in udev_is_md_array, Intel BIOS RAID array members are
wrongly identified as RAID arrays instead of as RAID array members, this
causes the actual raid array to not be seen by anaconda.
|
| |
|
|
|
|
|
| |
If the commit fails because there's an md array active on the disk
we will try again to add the partition after stopping the array, but
if we don't remove the failed-to-add partition first, we end up with
a mess.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
LVM (when looking for PVs) is finding the temporary udev device
instead of the real/final device, so this is to make sure things
are as they should be when lvm goes-a-hunting for devices.
We should probably be explicitly telling lvm which devices to look
for PVs on to avoid it scanning every block device every time we
run an lvm command.
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This also removes the hack where upgrade can be True, False, or None in order
to test whether we've seen the upgrade screen or not. Instead, it introduces
a global value hack. I consider this the slightly cleaner approach.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
anaconda.ksdata is only non-None if there's a kickstart file, just like
anaconda.isKickstart would be. Therefore, we don't need two variables
to test for the same condition.
|
| | |
| |
| |
| |
| | |
This is esp. important with DASD's as these will only accept properly
aligned partitions.
|
| | | |
|
| | |
| |
| |
| | |
Timestamp/tag format changed.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
MD_DEVNAME is never set for existing md arrays. Some metadata versions
will have MD_NAME, but not all. All md arrays have MD_METADATA while
component devices do not, making it perfect for differentiating them.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Given a partition layout like this:
partition startsector endsector
/boot 2048 1026047
PV 1026048 xxxxxxxxxx
Then when we call getFreeRegions() parted gives us a free region with a
geometry starting at sector 63 and ending at sector 2047, which we then try to
align to our 2048 grain, which fails for the starting sector. When we fail to
align, this means that the free region is too small to create an aligned
partition in there, and we should just skip it.
|
| |
|
|
| |
This is a leftover from having our own udev db reading code.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our partitioning code was assuming that having a partition from
sector 0 - 512 means the partition stops at sector 512, iow that
it goes from sector 0 till 511, but that is not how parted geometries
work, the range includes the end sector. So 0 - 512 will get you
a 513 sectors partition.
This patch adds an endAligment property to disklabel which can be used
to properly align end sectors (which must be aligned to the disklabel's
alignment with the offset decreased by 1), patches partitioning.py to
use this to align end sectors and fixes up end sector calculations in
partitioning.py to be start + length - 1.
On DASD's (s390), the wrong end sector was causing a traceback (#560586),
as DASD's disklabels need partitions to be cylinder aligned, and the wrong
end sector violated this.
|
| |
|
|
|
| |
When doing custom partitioning, and adding an mdraid array, and a pre-existing
array has a minor > 32, we will back trace, this patch fixes this.
|
