Bug#350861: [Yaird-devel] Bug#350861: yaird: Degraded RAID 1 array fails to boot

Shaun Jackman sjackman at gmail.com
Thu Feb 2 00:23:18 UTC 2006


> > On 2/1/06, Jonas Smedegaard <dr at jones.dk> wrote:
> > I agree with not including the mdadm.conf in the initrd. When the
> > initrd is built though, I'd check that the mdadm configuration stored
> > in the root disk's /init, which is tantamount to a config file, should
> > be checked against the host's mdadm.conf to ensure they match. If they
> > don't, I'd suggest yaird should fail. The user can then fix one or the
> > other.
>
> Don't understand. What does tantamount mean? And how can you be talking
> about comparing two different config files when none is included in the
> initrd and the one on the rootfs is only accessible _after_ suffesful
> mount?

s/tantamount/equivalent/

When yaird is run, not when the root disk boots, compare the mdadm
information yaird is going to write to /init, and compare that to the
mdadm.conf of the host running yaird. If they don't match, yaird
should fail.

Cheers,
Shaun




More information about the Yaird-devel mailing list