Though I can sure understand it would be easier if we could just dismiss this to be taken care of by users, data-loss/corruption will allways come back heavy on ubuntu/mdadm.
With ubunu systems in particular, we can not assume there will always be an admin available. And if there is an admin, and he allways has to re- add removed members manually, how does he notice if a user made conflicting changes? I am not sure if we are considering the valid use case of auto re-adding members enough here, yet. (Even if auto-adding just "missing" and not "removed" members.) I.e. the case of docking-stations / external backup drives. > You seem to be agreeing with me that automatically >adding the disk back and resyncing causes data loss, thus this should be >avoided. We need to avoid and warn about data-loss, no matter if manually or automatically. Re-adding needs to be safe operation. If concurrent changes where made syncing has to be refused, if --force is not used. > you should have to manually add the disk back. You >say this is how it used to work? When? It doesn't seem to work that >way on Karmic. If it used to work that way, then the fact that it no >longer does is the regression that needs fixed. Creating a fully hot-pluggable system is a major feature of ubuntu. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
