Hello, I got a bizzare problem after trying to upgrade from 3.7.10 (which works fine) to 3.8.3 or 3.9-rc3 (fail in the same way): It looks like on the newer kernels MD does not wait for all drives to finish registering before trying to bring up the arrays. As a result, on newer kernels my arrays always come up with only 5 out of 7 members active. dmesg 3.7.10: http://romanrm.ru/dl/mdadm/dmesg37.txt dmesg 3.9-rc3: http://romanrm.ru/dl/mdadm/dmesg39.txt As you can see on 3.7.10 drives continue to go online until about 3.89sec (Hitachi) and 4.26sec (card reader, unrelated), and only THEN, at 5.15sec the md0 starts; it has all drives and everything is good. On 3.9-rc3 (and 3.8.3), md0 tries to become active VERY EARLY at 2.64sec of boot-up!!! Of course missing drives which appear later, and of those, members of it should have been two Hitachi drives coming up at 3.33sec and 3.87sec. So it starts degraded with 5 of 7 devices only. What's up with this? I understand this might be not an md problem but an udev(?) one; but how do I go about solving this? -- With respect, Roman (resending this message since the previous one with largish attachments didn't seem to make it to the list; also used a different dmesg for 3.7)
Attachment:
signature.asc
Description: PGP signature
