Package: mdadm Version: 2.5.3-1~unreleased.3 Severity: normal Dear Neil,
Here's an issue I've stumbled over today: say /etc/mdadm/mdadm.conf refers to /dev/md1, but that does not exist during boot and udev does *not* create it. Now, check this out: mdadm:~# rm /dev/md? mdadm:~# mdadm -As mdadm: No arrays found in config file or automatically mdadm:~# ls /dev/md? /dev/md1 /dev/md5 /dev/md6 mdadm:~# mdadm -As mdadm: /dev/md5 is already active. mdadm: /dev/md1 is already active. mdadm: /dev/md6 is already active. So it seems that mdadm creates the device nodes even though it does not find any. On second try then, of course, it works. Strace of first run attached. I think this appeared with 2.5.3, or else a bug like http://bugs.debian.org/382263 would not have happened with 2.5.2. Short rundown: if devices are brought up before mdadm -A is run by init and udev does not create the /dev nodes, boots will fail to mount partitions or initialise LVM/crypt. -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED] spamtraps: [EMAIL PROTECTED] "die menschen drängen sich zum lichte, nicht um besser zu sehen, sondern um besser zu glänzen." - friedrich nietzsche
mdadm.strace.bz2
Description: Binary data
signature.asc
Description: Digital signature (GPG/PGP)
