https://bugzilla.novell.com/show_bug.cgi?id=798275 https://bugzilla.novell.com/show_bug.cgi?id=798275#c6 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|nfbrown@suse.com | --- Comment #6 from Neil Brown <nfbrown@suse.com> 2013-02-26 01:45:05 UTC --- I'm not sure if it was intention of accident, but it has always been that way, at least as long has it has been possible to mark devices as busy (2.6.0 I think). So I think the fact that it hasn't been reported before it just "luck". Presumably the array was left in this inactive state by mdadm, but that doesn't surprise me. It will normally only do that when you are assembling an array by hand: mdadm -A /dev/md0 /dev/sda1 for example. Normally the boot process does something like: mdadm -As which, I think, doesn't leave 'inactive' arrays. Do you know what would have started the array in this case? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.