Martchus
/
mdadm
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

mdadm.conf.5: clarify connection between action=re-add and bitmaps. 

action=re-add will only re-add a recently removed device if a
bitmap is present.
Otherwise a force-space is needed.

Signed-off-by: NeilBrown <neilb@suse.de>
This commit is contained in:
NeilBrown 2013-01-21 10:12:53 +11:00
parent 9dc7d3576a
commit e31dec228b
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
mdadm.conf.5
View File

@ -490,9 +490,12 @@ is irrelevant to the end result.
.B include
allows adding a disk to an array if metadata on that disk matches that array
.TP
.B re-add
.B re\-add
will include the device in the array if it appears to be a current member
or a member that was recently removed
or a member that was recently removed and the array has a
write-intent-bitmap to allow the
.B re\-add
functionality.
.TP
.B spare
as above and additionally: if the device is bare it can
@ -504,7 +507,7 @@ as above and additionally if given slot was used by an array that went
degraded recently and the device plugged in has no metadata then it will
be automatically added to that array (or it's container)
.TP
.B force-spare
.B force\-spare
as above and the disk will become a spare in remaining cases
.RE