Comment 13 for bug 925280

It looks like there have been some changes in mdadm behavior. They don't appear to be documented in the announcements, so they could be bugs.

First, it appears that --re-add now requires an intent bitmap. Second, incremental mode refuses to (re)add the disk to the array once it has started degraded. Finally, --add now seems to require --run to reinsert the disk.

If these changes were intentional, then I suppose that the test procedure needs updated. I'll ask on the mailing list. If they were intentional, then the test procedure should say that you need to enable the write intent bitmap and manually --re-add the disk, or --add --run without a bitmap.