diff options
author | NeilBrown <neilb@suse.de> | 2012-03-18 21:46:37 -0400 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2012-03-18 21:46:37 -0400 |
commit | dc10c643e8a8d008fd16dd6706e9e0018eadf8d2 (patch) | |
tree | 6a0efe323cfaca9d180c0429c74697598c6d9a05 /drivers/md/md.c | |
parent | 41fe75f60bcd4d698daed3e54bb099227358ce58 (diff) |
md: allow re-add to failed arrays.
When an array is failed (some data inaccessible) then there is no
point attempting to add a spare as it could not possibly be recovered.
However that may be value in re-adding a recently removed device.
e.g. if there is a write-intent-bitmap and it is clear, then access
to the data could be restored by this action.
So don't reject a re-add to a failed array for RAID10 and RAID5 (the
only arrays types that check for a failed array).
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/md.c')
0 files changed, 0 insertions, 0 deletions