> My current thinking is that the initramfs should *only* assemble > arrays needed > to mount the root filesystems. All other arrays should wait for root > to be > mounted so that real /etc/mdadm.conf (or /etc/mdadm/mdadm.conf) can be > consulted. > This can be achieved by putting > auto -all > in mdadm.conf on the initramfs, then listing the arrays that are > needed. > > I'm not convinced that your boot-degraded option is a bad thing. > Certainly > it should be optional so unattended boot is possible, and we should do > our > best to minimise the number of times that it is consulted. But there > are > times when it is better to know that something is wrong, than to > proceed and > do the wrong thing. > > A particularly bad case is a RAID1 pair where one device failed a few > days > ago. > If after a reboot the good device is missing (cable problem?) and the > bad > device is visible, it could be best not to boot rather than to boot > with an > old root based on the old 'failed' device. Anyone that knows more about this issue and how to fix it? I've filed a bug, but haven't gotten any more feedback -- Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 98013356 roy@xxxxxxxxxxxxx http://blogg.karlsbakk.net/ GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
