Blame SOURCES/0059-mdadm.8-add-note-information-for-raid0-growing-opera.patch

5bf14f
From 2551061c253b8fd45ee93d1aab3e91d2c7ac9c20 Mon Sep 17 00:00:00 2001
5bf14f
From: Coly Li <colyli@suse.de>
5bf14f
Date: Mon, 24 Feb 2020 12:34:09 +0100
5bf14f
Subject: [RHEL7.9 PATCH 59/71] mdadm.8: add note information for raid0 growing
5bf14f
 operation
5bf14f
5bf14f
When growing a raid0 device, if the new component disk size is not
5bf14f
big enough, the grow operation may fail due to lack of backup space.
5bf14f
5bf14f
The minimum backup space should be larger than:
5bf14f
 LCM(old, new) * chunk-size * 2
5bf14f
5bf14f
where LCM() is the least common multiple of the old and new count of
5bf14f
component disks, and "* 2" comes from the fact that mdadm refuses to
5bf14f
use more than half of a spare device for backup space.
5bf14f
5bf14f
There are users reporting such failure when they grew a raid0 array
5bf14f
with small component disk. Neil Brown points out this is not a bug
5bf14f
and how the failure comes. This patch adds note information into
5bf14f
mdadm(8) man page in the Notes part of GROW MODE section to explain
5bf14f
the minimum size requirement of new component disk size or external
5bf14f
backup size.
5bf14f
5bf14f
Reviewed-by: Petr Vorel <pvorel@suse.cz>
5bf14f
Cc: NeilBrown <neilb@suse.de>
5bf14f
Cc: Jes Sorensen <jsorensen@fb.com>
5bf14f
Cc: Paul Menzel <pmenzel@molgen.mpg.de>
5bf14f
Cc: Wols Lists <antlists@youngman.org.uk>
5bf14f
Cc: Nix <nix@esperi.org.uk>
5bf14f
Signed-off-by: Coly Li <colyli@suse.de>
5bf14f
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
5bf14f
---
5bf14f
 mdadm.8.in | 6 ++++++
5bf14f
 1 file changed, 6 insertions(+)
5bf14f
5bf14f
diff --git a/mdadm.8.in b/mdadm.8.in
5bf14f
index 5d00faf..a3494a1 100644
5bf14f
--- a/mdadm.8.in
5bf14f
+++ b/mdadm.8.in
5bf14f
@@ -2768,6 +2768,12 @@ option and it is transparent for assembly feature.
5bf14f
 .IP \(bu 4
5bf14f
 Roaming between Windows(R) and Linux systems for IMSM metadata is not
5bf14f
 supported during grow process.
5bf14f
+.IP \(bu 4
5bf14f
+When growing a raid0 device, the new component disk size (or external
5bf14f
+backup size) should be larger than LCM(old, new) * chunk-size * 2,
5bf14f
+where LCM() is the least common multiple of the old and new count of
5bf14f
+component disks, and "* 2" comes from the fact that mdadm refuses to
5bf14f
+use more than half of a spare device for backup space.
5bf14f
 
5bf14f
 .SS SIZE CHANGES
5bf14f
 Normally when an array is built the "size" is taken from the smallest
5bf14f
-- 
5bf14f
2.7.5
5bf14f