summaryrefslogtreecommitdiffstats
path: root/mdadm.8
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-07-13 15:00:02 +1000
committerNeilBrown <neilb@suse.de>2009-07-13 15:00:02 +1000
commit84e11361aa37c92c3c016095e5db7f4fc434ac18 (patch)
tree784d588a80d609f857beef00107adda2cc7b10d8 /mdadm.8
parente0d95aac9626badd1b849ce4f99f9c406d55beae (diff)
downloadmdadm-84e11361aa37c92c3c016095e5db7f4fc434ac18.tar.gz
mdadm-84e11361aa37c92c3c016095e5db7f4fc434ac18.tar.xz
mdadm-84e11361aa37c92c3c016095e5db7f4fc434ac18.zip
Grow: support --array-size changes
With 2.6.30 it is possible to tell the md driver to clip an array to a size smaller than the real size of the array. This option gives access to that feature. The size change does not persist across restarts. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdadm.8')
-rw-r--r--mdadm.815
1 files changed, 15 insertions, 0 deletions
diff --git a/mdadm.8 b/mdadm.8
index 3b4f47d..079914f 100644
--- a/mdadm.8
+++ b/mdadm.8
@@ -594,6 +594,21 @@ See the section below on RAID_DEVICE CHANGES. The file should be
stored on a separate device, not on the raid array being reshaped.
.TP
+.BR \-\-array-size= ", " \-Z
+Set the size of the array which is seen by users of the device such as
+filesystems. This can be less that the real size, but never greater.
+The size set this way does not persist across restarts of the array.
+
+This is most useful when reducing the number of devices in a RAID5 or
+RAID6. Such arrays require the array-size to be reduced before a
+reshape can be performed that reduces the real size.
+
+A value of
+.B max
+restores the apparent size of the array to be whatever the real
+amount of available space is.
+
+.TP
.BR \-N ", " \-\-name=
Set a
.B name