Hans de Goede wrote:
Hi,
On 07/14/2009 07:47 PM, David Lehman wrote:
On Fri, 2009-07-10 at 15:10 +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.
Have we filed a bug against mdadm for this? Or is this somehow not a
bug?
Well this only happens for containers (so BIOS raid using mdadm, the new
intel stuff) and I've talked to Dan Williams about this (who has done
most of the imsm mdadm code) and he considered this normal behaviour ?
Incremental mode will try to run an array as soon as it is feasible.
The container is runnable with any number of disks so we need to hold
off starting the container until all member disks and hot spares have
been added to the container. This option also covers the case where
stale disks are initially added to the container at the start of
discovery. We want to wait until discovery completes as it may find
newer metadata on later members that identifies stale disks and prevents
them from being re-activated.
So it is blocking too early assembly.
Regards,
Dan
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
