http://bugzilla.novell.com/show_bug.cgi?id=557612 http://bugzilla.novell.com/show_bug.cgi?id=557612#c shuang qiu changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com Severity|Major |Normal -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557612 http://bugzilla.novell.com/show_bug.cgi?id=557612#c2 Neil F Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Neil F Brown 2009-11-29 03:57:50 UTC --- Hi Jon. /dev/mdXX is the actual device. /dev/md/XX should be a symlink to that device. I'm surprised that ever worked. As md1 depends on md12, it should be listed later in mdadm.conf. I'll see if I can recreate this situation on 11.1 and see how it works. My only guess is that maybe 11.1 runs "mdadm -As" twice (once from initrd, once at regular boot??). NeilBrown -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557612 http://bugzilla.novell.com/show_bug.cgi?id=557612#c4 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |jnelson-suse@jamponi.net --- Comment #4 from Neil Brown 2009-11-30 23:36:19 UTC --- It shouldn't be strange. mdadm simply processes the array listed in mdadm.conf in order. As md1 cannot be assembled before md12 exists, it should not be a surprise that md12 needs to be before md1. When you say this worked in 11.1, was it with exactly the same config file, or was it just the same configuration with a possibly different config file? If the latter, is there any chance that you have a backup of the old config file? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557612 http://bugzilla.novell.com/show_bug.cgi?id=557612#c6 --- Comment #6 from Neil Brown 2009-12-15 05:02:22 UTC --- I finally got around to comparing 11.1 (or 11.0 actually) with 11.2. It seems that in 11.1, the initrd scripts will try to activate all arrays listed in /etc/mdadm.conf, Then the regular boot scripts will try again. This doubling up allowed md/12 to assembled in the initrd, then md1 to be assembled by /etc/init.d/boot.md. In 11.2, the initrd only assembled the arrays that are needed to find the root, so md/12 is no longer assembled in the initrd, so boot.md is not able to assemble md1 - until you changed the order in mdadm.conf so: - could close this bug as 'invalid' because there was a configuration error which just happened to work before - by accident. - or maybe we should see this is a feature request - presumably you used "mdadm -Ds" or "mdadm -Es" to help generate mdadm.conf and maybe they should be clever enough to get the order of array right. I don't think I want to try to get mdadm -[ED]s to sort things. The "preferred" way to start arrays should be to use "mdadm -I" from udev. This completely avoids any ordering issues in mdadm.conf. So maybe I should make a feature request for mdadm -I to be used in udev... or maybe I'll do that latter... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.