Blame SOURCES/0059-imsm-Update-grow-manual.patch

2910d5
From 4431efebabd0dd39f33dc1dd8ada312b8da1c9d8 Mon Sep 17 00:00:00 2001
2910d5
From: Blazej Kucman <blazej.kucman@intel.com>
2910d5
Date: Thu, 16 Jan 2020 09:34:44 +0100
2910d5
Subject: [RHEL8.2 PATCH 59/61] imsm: Update grow manual.
2910d5
2910d5
Update --grow option description in manual, according to
2910d5
the supported grow operations by IMSM.
2910d5
2910d5
Signed-off-by: Blazej Kucman <blazej.kucman@intel.com>
2910d5
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
2910d5
---
2910d5
 mdadm.8.in | 8 ++------
2910d5
 1 file changed, 2 insertions(+), 6 deletions(-)
2910d5
2910d5
diff --git a/mdadm.8.in b/mdadm.8.in
2910d5
index 6b63bb4..ca02a33 100644
2910d5
--- a/mdadm.8.in
2910d5
+++ b/mdadm.8.in
2910d5
@@ -481,9 +481,7 @@ still be larger than any replacement.
2910d5
 This value can be set with
2910d5
 .B \-\-grow
2910d5
 for RAID level 1/4/5/6 though
2910d5
-.B CONTAINER
2910d5
-based arrays such as those with IMSM metadata may not be able to
2910d5
-support this.
2910d5
+DDF arrays may not be able to support this.
2910d5
 If the array was created with a size smaller than the currently
2910d5
 active drives, the extra space can be accessed using
2910d5
 .BR \-\-grow .
2910d5
@@ -2759,9 +2757,7 @@ container format.  The number of devices in a container can be
2910d5
 increased - which affects all arrays in the container - or an array
2910d5
 in a container can be converted between levels where those levels are
2910d5
 supported by the container, and the conversion is on of those listed
2910d5
-above.  Resizing arrays in an IMSM container with
2910d5
-.B "--grow --size"
2910d5
-is not yet supported.
2910d5
+above.
2910d5
 
2910d5
 .PP
2910d5
 Notes:
2910d5
-- 
2910d5
2.7.5
2910d5