Solving this bug will require a non-trivial overhaul of mdadm's failure hooks in the initramfs, and potentially new code in mdadm itself.
In my opinion, this is not something that can be solved in Lucid by release. Also in my opinion, this is not a release critical issue, but rather should be addressed in the 10.04 release notes. As such, I'm marking this bug won't-fix for Lucid, but leaving it triaged for the next development cycle (Maverick), and unassigning myself. I can see where one of the bug's subscribers has written a spec on what they believe to be a better design for mdadm/initramfs failure handling: * https://wiki.ubuntu.com/ReliableRaid Someone from the Ubuntu Foundations Team or the Ubuntu Community can propose this spec at UDS-Maverick in May, and perhaps implement the re- design in the next release. But the time has past for this level of feature development in Lucid. Cheers, :-Dustin ** Changed in: mdadm (Ubuntu Lucid) Assignee: Dustin Kirkland (kirkland) => (unassigned) ** Changed in: mdadm (Ubuntu Lucid) Status: Triaged => Won't Fix -- array with conflicting changes is assembled with data corruption/silent loss https://bugs.launchpad.net/bugs/557429 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
