summaryrefslogtreecommitdiff
path: root/mdadm.conf.5
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2013-01-21 10:12:53 +1100
committerNeilBrown <neilb@suse.de>2013-01-21 10:12:53 +1100
commite31dec228bbe68c55f8e601500f82c9492c96aae (patch)
tree267e2ed975ad669a8475faca41d1a4843f9f4d3c /mdadm.conf.5
parent9dc7d3576a2c0be1b113088ef1841bbfe24374a6 (diff)
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>
Diffstat (limited to 'mdadm.conf.5')
-rw-r--r--mdadm.conf.59
1 files changed, 6 insertions, 3 deletions
diff --git a/mdadm.conf.5 b/mdadm.conf.5
index 48822df8..8a21fcc4 100644
--- a/mdadm.conf.5
+++ b/mdadm.conf.5
@@ -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