diff options
| author | Blazej Kucman <blazej.kucman@intel.com> | 2020-01-16 09:34:44 +0100 |
|---|---|---|
| committer | Jes Sorensen <jsorensen@fb.com> | 2020-01-16 13:56:10 -0500 |
| commit | 4431efebabd0dd39f33dc1dd8ada312b8da1c9d8 (patch) | |
| tree | f5909c0833288db89a51ae29152780b8396e8d5a | |
| parent | e1512e7b7d060f0346738b237ea34eac21b29a26 (diff) | |
| download | mdadm-4431efebabd0dd39f33dc1dd8ada312b8da1c9d8.tar.gz | |
imsm: Update grow manual.
Update --grow option description in manual, according to
the supported grow operations by IMSM.
Signed-off-by: Blazej Kucman <blazej.kucman@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
| -rw-r--r-- | mdadm.8.in | 8 |
1 files changed, 2 insertions, 6 deletions
@@ -481,9 +481,7 @@ still be larger than any replacement. This value can be set with .B \-\-grow for RAID level 1/4/5/6 though -.B CONTAINER -based arrays such as those with IMSM metadata may not be able to -support this. +DDF arrays may not be able to support this. If the array was created with a size smaller than the currently active drives, the extra space can be accessed using .BR \-\-grow . @@ -2759,9 +2757,7 @@ container format. The number of devices in a container can be increased - which affects all arrays in the container - or an array in a container can be converted between levels where those levels are supported by the container, and the conversion is on of those listed -above. Resizing arrays in an IMSM container with -.B "--grow --size" -is not yet supported. +above. .PP Notes: |