From 4431efebabd0dd39f33dc1dd8ada312b8da1c9d8 Mon Sep 17 00:00:00 2001 From: Blazej Kucman Date: Thu, 16 Jan 2020 09:34:44 +0100 Subject: [PATCH] imsm: Update grow manual. Git-commit: 4431efebabd0dd39f33dc1dd8ada312b8da1c9d8 Patch-mainline: mdadm-4.1+ References: jsc#SLE-10078, jsc#SLE-9348 Update --grow option description in manual, according to the supported grow operations by IMSM. Signed-off-by: Blazej Kucman Signed-off-by: Jes Sorensen Signed-off-by: Coly Li --- mdadm.8.in | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/mdadm.8.in b/mdadm.8.in index 6b63bb4..ca02a33 100644 --- a/mdadm.8.in +++ b/mdadm.8.in @@ -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: -- 2.25.0