diff options
| author | NeilBrown <neilb@suse.de> | 2011-02-15 12:40:21 +1100 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2011-02-15 12:40:21 +1100 |
| commit | c26d78fe040673b019e1c2e4a5507969d2869765 (patch) | |
| tree | fc92e15847072ad15bee022894766a965ba46cde /mdadm.8.in | |
| parent | 5b660791b4afb9b24b13cbf4877ea62e4e832537 (diff) | |
mdadm.man add encouragement to shrink filesystem before shrinking array.
Before resizing an array with --size or --array-size, then filesystem
should be resized. mdadm cannot do this so the user should.
Reported-by: Gavin Flower <gavinflower@yahoo.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdadm.8.in')
| -rw-r--r-- | mdadm.8.in | 25 |
1 files changed, 24 insertions, 1 deletions
@@ -427,12 +427,24 @@ The size can be given as .B max which means to choose the largest size that fits on all current drives. +Before reducing the size of the array (with +.BR "\-\-grow \-\-size=" ) +you should make sure that space isn't needed. If the device holds a +filesystem, you would need to resize the filesystem to use less space. + +After reducing the array size you should check that the data stored in +the device is still available. If the device holds a filesystem, then +an 'fsck' of the filesystem is a minimum requirement. If there are +problems the array can be made bigger again with no loss with another +.B "\-\-grow \-\-size=" +command. + This value can not be used with .B CONTAINER metadata such as DDF and IMSM. .TP -.BR \-Z ", " \-\-array-size= +.BR \-Z ", " \-\-array\-size= This is only meaningful with .B \-\-grow and its effect is not persistent: when the array is stopped and @@ -446,6 +458,17 @@ but setting the size with is, it is required that the array size is reduced as appropriate before the number of devices in the array is reduced. +Before reducing the size of the array you should make sure that space +isn't needed. If the device holds a filesystem, you would need to +resize the filesystem to use less space. + +After reducing the array size you should check that the data stored in +the device is still available. If the device holds a filesystem, then +an 'fsck' of the filesystem is a minimum requirement. If there are +problems the array can be made bigger again with no loss with another +.B "\-\-grow \-\-array\-size=" +command. + A suffix of 'M' or 'G' can be given to indicate Megabytes or Gigabytes respectively. A value of |