On Tue, 2009-07-14 at 22:38 +0200, Hans de Goede wrote:
> We do not want to bring arrays up (and esp not use, so not scan them) in
> degraded mode, so add --no-degraded to the mdadm invocation.
>
> Note we do not add --no-degraded to the mdadm invocation for the last
> disk of the set, because doing so assembles the array in an inactive
> (and thus unusable) state.
Aside from the fact that this seems to be a bug in mdadm that we should
not be writing code around, this whole set looks reasonable.
Dave
> ---
> storage/devices.py | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/storage/devices.py b/storage/devices.py
> index b46479b..f3f29a4 100644
> --- a/storage/devices.py
> +++ b/storage/devices.py
> @@ -2426,7 +2426,7 @@ class MDRaidArrayDevice(StorageDevice):
> device.setup()
> udev_settle(timeout=10)
> try:
> - mdraid.mdadd(device.path)
> + mdraid.mdadd(device.path, len(self.devices) < self.memberDevices)
> except MDRaidError as e:
> log.warning("failed to add member %s to md array %s: %s"
> % (device.path, self.path, e))
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
