I agree with Philip's assessment. While this is very easy to reproduce in a VM (by just removing/adding backing disk files), in practice and on real hardware, I think this is definitely less likely.
When a real hardware disk fails, it should be removed from the system, and not come back until it's replaced with new hardware, in which case this bug will not be triggered. As Philip explained, this would only happen if an admin is adding and removing and booting with just one disk, and then the other, and then both. Don't do that. -- 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
