So after letting the server sit for a few hours, all missing members of the arrays have been re-synced and are functional again. Perhaps this behaviour IS correct. Most of my RAID experience is with hardware RAID, admittedly, so I'm used to just swapping a disk out and the controller would handle adding/re-syncing automatically. I've not done a lot of degradation testing with software RAID and having to go to these extra lengths may well be standard behaviour.
IN any case, if this is truly expected behaviour, the test case then
So after letting the server sit for a few hours, all missing members of the arrays have been re-synced and are functional again. Perhaps this behaviour IS correct. Most of my RAID experience is with hardware RAID, admittedly, so I'm used to just swapping a disk out and the controller would handle adding/re-syncing automatically. I've not done a lot of degradation testing with software RAID and having to go to these extra lengths may well be standard behaviour.
IN any case, if this is truly expected behaviour, the test case then
http:// testcases. qa.ubuntu. com/Install/ ServerRAID1
should be updated to reflect this. (assuming, of course, it is decided that this is not a bug after all).