Comment 26 for bug 557429

Currently mdadm does not seem to distingush manual --removed status from the status a drive that is missing gets when the array is run degraded.

Especially with write intent bitmaps regulary being used for faster syncing in hotplug setups, and mdadm only comparing if "eventcount is in range of bitmap":

* Fixing this "data-loss on conflicting changes" bug, will require a better detection of conflicts.
* Support for tracking explicitly --removed disks in the superblocks to prevent their auto-re-addition, is a valid but separate issue as far as I am concerned.