| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Timestamp/tag format changed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
| |
This should reduce the dogpiling in bugzilla for overly-generic
errors like "lvcreate failed for VolGroup/lv_root".
|
|
|
|
|
|
| |
Passing --update=super-minor to mdadm for containers and sets there in
leads to corrupt superblocks, see: bug rh523320, work around this for now
by not passing --update=super-minor in these cases.
|
|
|
|
| |
This patch adds new class MDRaidContainerDevice.
|
| |
|
| |
|
|
|
|
|
|
| |
Having run as the first argument sets the mode to miscellaneous,
which is not what we want -- we want assembly mode since we are
assembling an array.
|
|
|
|
|
|
| |
I didn't want to add another 0/'0'/'RAID0' tweaking so I made
mdraid.raid_levels and mdraid deviceclass level attribute to contain
constants for levels defined in mdraid.py.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* We get RAID1 from ks parser, mdadm accepts only lowercase level
specifiers of this form.
* We get int device number (e.g. 0) from ks option --device (e.g. md0).
Though this might require rather changes in pykickstart, especially
when mdadm 3.0 allows creating of arbitrary device names in /dev/md.
* mdadm --create --level option is changed to comply strictly to
documentation (e.g. "--level=raid0", though "--level raid0" works too)
|
| |
|
|
|
|
|
| |
This was either to work around a bug in mdadm or my bad usage, but
either way it is no longer necessary.
|
|
|
|
|
|
| |
This only fixes the serious errors that may affect F11 Beta. There's still
a lot of patch left that fixes some more nitpicky stuff which can come in
later.
|
|
|
|
| |
(#490891)
|
|
|
|
|
|
|
|
|
|
| |
Rewrote the devicelibs unittest baseclass so we can create and remove another loop devices within the tests.
Rewrote the isRaidXY(raidlevel) functions in mdraid.py into one function isRaid(XY, raidlevel).
Rewrote the get_raid_min_members and get_raid_max_spares functions
to use the new isRaid function, and not use many if-elif-else statements.
Changed the minimum raid members for raid10 to 2.
|
| |
|
|
|
|
|
|
| |
Also catch exceptions thrown by platform.bootDevice() and add
mdRaidBootArches from old raid.py to storage.devicelibs.mdraid
for use by the sanityCheck code.
|
|
|
|
|
|
|
|
|
|
|
| |
- Change minsize/maxsize to minSize/maxSize since that's the
convention elsewhere throughout the code.
- Redirect output from all external utilities to tty5, not
/dev/null.
- Don't waste calls to basename for debug log statements,
especially when the device can be None.
- Add lots of missing imports.
- Fix lots of remnants of previous code usage.
|
| |
|
|
|