summaryrefslogtreecommitdiff
path: root/mdadm.8.in
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2011-05-16 17:28:27 +1000
committerNeilBrown <neilb@suse.de>2011-05-16 17:28:27 +1000
commitce52f92f047a1d95246b20c091e2cc342af919bf (patch)
tree8834b26991175933f49393cdd8f6c7efbf92bf5c /mdadm.8.in
parentab80e597bae3df0209135a4130c93f57d5eb3e34 (diff)
Grow: accept --assume-clean with --grow --size
When an array is resized to have larger members, --assume-clean will disable any resync if the kernel supports it (2.6.40 and later). Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdadm.8.in')
-rw-r--r--mdadm.8.in7
1 files changed, 7 insertions, 0 deletions
diff --git a/mdadm.8.in b/mdadm.8.in
index 3fbfcce8..e1d5651d 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -702,6 +702,13 @@ with zeros before creation the operator knows the array is
actually clean. If that is the case, such as after running
badblocks, this argument can be used to tell mdadm the
facts the operator knows.
+.IP
+When an array is resized to a larger size with
+.B "\-\-grow \-\-size="
+the new space is normally resynced in that same way that the whole
+array is resynced at creation. From Linux version 2.6.40,
+.B \-\-assume\-clean
+can be used with that command to avoid the automatic resync.
.TP
.BR \-\-backup\-file=