https://bugzilla.novell.com/show_bug.cgi?id=641382 https://bugzilla.novell.com/show_bug.cgi?id=641382#c2 --- Comment #2 from Kay Sievers 2010-09-23 19:43:46 UTC --- Something is running in a loop. Probably the weird behavior of md, which tries to instantiate a md device just by having its device node accessed. The access probably happens from an earlier/delayed udev event. Not sure, how udev can work around such unfortunate behavior. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=641382 https://bugzilla.novell.com/show_bug.cgi?id=641382#c4 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |nfbrown@novell.com InfoProvider|nfbrown@novell.com | --- Comment #4 from Neil Brown 2010-09-25 07:16:21 UTC --- Why is it instantly destroyed again? md devices are only auto-destroyed on last close (when not inactive) is some md ioctl (or similar sysfs access) has happened on the device. So just opening an closing the device will leave existing (but inactive). What is udev doing to the device between it appearing and it disappearing? Maybe it is just a GET_ARRAY_INFO syscall... I guess we should arrange that that doesn't cause the device to disappear. So: if I can find out exactly what is being done to the md array between it appearing and it disappearing I can probably work something out. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=641382 https://bugzilla.novell.com/show_bug.cgi?id=641382#c6 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |aschnell@novell.com --- Comment #6 from Neil Brown 2010-10-18 05:05:05 UTC --- Hi Arvin, can you please try editing /lib/udev/rules.d/64-md-raid.rules and add the line TEST!="md/array_state", GOTO="md_end" just after # container devices have a metadata version of e.g. 'external:ddf' and # never leave state 'inactive' and then see if you can reproduce the problem. Thanks. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=641382 https://bugzilla.novell.com/show_bug.cgi?id=641382#c8 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |aschnell@novell.com --- Comment #8 from Neil Brown 2010-10-21 01:22:59 UTC --- Great. I'll see about incorporating that into the package. I'm tempted to go to the lastest upstream release, but that changes the default metadata type so we need some serious testing. Maybe you could help me: Does yast-storage just use the default that mdadm chooses, or does it always set a default? Do you have any idea how it would cope if the default changed from 0.90 to 1.2 ?? Thanks. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=641382 https://bugzilla.novell.com/show_bug.cgi?id=641382#c Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=641382 https://bugzilla.novell.com/show_bug.cgi?id=641382#c12 --- Comment #12 from Dirk Mueller 2011-04-18 13:05:41 CEST --- this comment seems to indicate that: https://bugzilla.novell.com/show_bug.cgi?id=668014#c124 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=641382 https://bugzilla.novell.com/show_bug.cgi?id=641382#c19 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:sle11-sp1:40 | |580 --- Comment #19 from Swamp Workflow Management 2011-05-13 03:18:04 UTC --- Update released for: mdadm, mdadm-debuginfo, mdadm-debugsource Products: SLE-DEBUGINFO 11-SP1 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11-SP1 (i386, x86_64) SLE-SERVER 11-SP1 (i386, ia64, ppc64, s390x, x86_64) SLES4VMWARE 11-SP1 (i386, x86_64) -- 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.