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

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