| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Since we're using the multipath tools, we don't need to group by serial.
Also don't use the name generator.
|
|
|
|
|
| |
This adds an exception to use when multipath (and related utilities)
fail.
|
|
|
|
|
| |
Call log_method_call() in MultipathDevice.addParent() and
Device.setupParents()
|
|
|
|
|
|
| |
devicetree.teardownAll() often causes storage errors which all get
ignored, but we've been enumerating them individually. use their
superclass instead.
|
|
|
|
|
| |
Prepend log_method_call()'s output with spaces corresponding to the
depth of the current call stack, so you can see what's calling what.
|
|
|
|
|
| |
iutil.execWithRedirect() stopped doing anything with searchPath in 2006
when clumens committed d0dec24. Remove these silly vestigal bits.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been running pylint on a subset of anaconda:
booty storage iw/*.py platform.py
And it has found various errors this commit fixes:
- Restore line accidently dropped from iscsi.py
- execWithPulseProgress should propagate the return value of
execWithCallback
- storage.formats.fs:535 (FS.doCheck): self.intf should be just intf
- storage.formats.fs: add missing "import sys" (for sys.exit)
- advanced_config.py add missing import for NetworkConfigurator
- lvm_dialog_gui.py: VolumeGroupEditor.editLogicalVolume dev was renamed to d
- partition_gui.py: remove an unneeded semicolon
- partition_gui.py: PartitionWindow.createCB rc should be dialog_rc
- storage.FSSet.write: put docstring in the proper place
- platform.Sparc.minimumSector: sectors should be sector
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As discussed on the mailinglist, mdadm will be moving to creating
version 1.1 metadata by default, and we should be creating arrays with
bitmaps (except for /boot and swap).
So this patch adds parameters to mdcreate to specify wether to use a
bitmap or not and which metadata version to use.
It then changes MDRaidArrayDevice.create() to:
1) For /boot force metadata version to 1.0, as grub cannot handle 1.1,
and don't use a bitmap.
2) For swap don't use a bitmap.
3) Everything else create with bitmap
|
| |
|
|
|
|
|
|
| |
If an unpartitionable device contains a disklabel we ignore any
partitions on that device, but we want to show that the device
does contain a partition table in UI.
|
|
|
|
| |
This way lvm lvs containing a disklabel will not be treated like disks.
|
|
|
|
|
|
|
|
|
| |
This becomes important when removing a disklabel from a device
which has a disklabel and partitions but which is not something
we support partitioning (eg: lvm lv). In normal cases the
partitions will already have been removed, but in the case of
an unsupported partitioned device we ignore the partitions when
scanning and so have to remove them this way.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The patch does essentially the same thing as commit
31d5b8f4fec513e4f8e246e47e9fee75c701d07b for disk initialization question. The
difference is that when user chooses LVM reinitialization, it is done
immediately (not as planned action as with disk initialization) so the user
wouldn't be asked again anyway without the patch (he would be asked if he chose
to ignore).
I also made one function more readable in the patch.
|
|
|
|
|
|
|
|
| |
Don't ask again and again e.g. when going back and forth in custom partitioning
UI. Related to bug #527711 which is itself fixed by another patch.
(*) Answers are cached in InstallInterface classes.
(*) Dialog callback is moved from storage code to InstallInterface
classes.
|
|
|
|
|
| |
Handle the special case of an empty list as if it were an infinitely
long list of disks.
|
| |
|
|
|
|
|
|
| |
We want to move to using dracut in such a way that the initrd only
activates the minimum of storage needed to bring up the root fs. This
requires us to tell it exactly what storage to activate.
|
|
|
|
|
| |
A timestamp in the keys will allow multiple installs (live media) as
well as arbitrary amounts of back and forth, resetting, whatever.
|
|
|
|
|
|
|
| |
This attribute is a dict that describes the device or format instance
with considerable detail. It is intended that the dict will be
pickled using the shelve module, so values should be picklable objects.
Keys should be descriptive strings.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
device.raidSet.name == device.name, so there is no need to specially
add it to ignore disks, this will only lead to the raidset name being
in ignoredDisks twice.
|
| |
|
| |
|
|
|
|
| |
This brings the behavior in line with other (dmraid) biosraid members.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The fcoe, iscsi and zfcp classes are designed to be instantiated only once,
currently this is not enforced. This is causing trouble as their single
instantiation currently is done in storage.__init__, which means they cannot
be used before instData is instantiated, as that instantiates storage.
However we need them to connect to fcoe, iscsi and/or zfcp drives while
parsing kickstart files (so the drivers can be referenced by UUID /
/dev/disk/by-path / whatever), and instData is not yet instantiated at that
time.
So this patch uses a very simple Singleton design pattern, so that we can
instantiate them where ever we need them, and all references returned will
will point to one shared global instance.
|
| |
|
|
|
|
|
| |
Unfortunately, the udev data for CCISS does not contain MD_* so I can't use
the udev_device_is_md to key off. This will have to do.
|
|
|
|
|
|
|
|
| |
The return type has also changed. It now returns a tuple of a list of regular
devices, a list of multipath sets, and a list of partition devices. This is
necessary so the filtering UI can use the same knowledge that was in the
DeviceTree object to know which devices are part of a multipath set and which
are just standalone disks.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
-Improve iscsi error logging
-Use udev_settle from udev.py instead of calling udevadm ourselves
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) centralize the setting of the timeout parameter inside the
udev_settle function. I do realize that the time needed for
initially scanning all disks is much larger, then the time for
scanning a single new partition when we are creating partitions.
But since this is a timeout, and udevadm settle will exit as soon
as the scanning is done, I see no reason not to have a single place
to configure the timeout assuming the worst case scenario (the initial
disk scan). This way we won't have these magic values sprinkled all
over the code.
2) Given that in the past we've had bugs filed
about anaconda taking many minutes to scan hardware on big iron machine
and that our initial udev settle call will scan all disks, I think
that udevadm's default timeout of 1 minutes is too low, so this patch
sets the timeout to 5 minutes.
|
|
|
|
|
|
|
|
|
|
|
| |
In F11 and F12 the command line option to enable btrfs during the installer was
"icantbelieveitsnotbtr". Unfortunately I can't spell believe the first time
every time, and btrfs has come quite a ways since F11 and is stable enough to
start being tested on a larger scale. So change the command line option to
"btrfs" in keeping with tradition and to make it a bit simpler for those who
want to take it for a test spin in F13. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
|
| |
|