summaryrefslogtreecommitdiff
path: root/mdadm.8.in
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2010-11-30 16:46:01 +1100
committerNeilBrown <neilb@suse.de>2010-11-30 16:46:01 +1100
commit5a31170d95236fdfd35a62cd3d7345ac43a75104 (patch)
tree1544cccc6e7c911dfbee9411117cce80768c2c96 /mdadm.8.in
parentff63406404b1a715282180570af7a4f1afabe634 (diff)
Assemble: add --update=no-bitmap
This allows an array with a corrupt internal bitmap to be assembled without the bitmap. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdadm.8.in')
-rw-r--r--mdadm.8.in9
1 files changed, 8 insertions, 1 deletions
diff --git a/mdadm.8.in b/mdadm.8.in
index 1cfd9170..4fc94396 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -903,6 +903,7 @@ argument given to this flag can be one of
.BR resync ,
.BR byteorder ,
.BR devicesize ,
+.BR no\-bitmap ,
or
.BR super\-minor .
@@ -985,7 +986,7 @@ counts of total, working, active, failed, and spare devices.
The
.B devicesize
-will rarely be of use. It applies to version 1.1 and 1.2 metadata
+option will rarely be of use. It applies to version 1.1 and 1.2 metadata
only (where the metadata is at the start of the device) and is only
useful when the component device has changed size (typically become
larger). The version 1 metadata records the amount of the device that
@@ -999,6 +1000,12 @@ This will cause
to determine the maximum usable amount of space on each device and
update the relevant field in the metadata.
+The
+.B no\-bitmap
+option can be used when an array has an internal bitmap which is
+corrupt in some way so that assembling the array normally fails. It
+will cause any internal bitmap to be ignored.
+
.ig
.TP
.B \-\-auto\-update\-homehost