Blame SOURCES/0014-Grow-block-n-on-external-volumes.patch

b33395
From 20e114e334ed6ed3280c37a9a08fb95578393d1a Mon Sep 17 00:00:00 2001
b33395
From: Mateusz Kusiak <mateusz.kusiak@intel.com>
b33395
Date: Thu, 19 May 2022 09:16:08 +0200
2ad819
Subject: [PATCH 14/83] Grow: block -n on external volumes.
b33395
b33395
Performing --raid-devices on external metadata volume should be blocked
b33395
as it causes unwanted behaviour.
b33395
b33395
Eg. Performing
b33395
mdadm -G /dev/md/volume -l10 -n4
b33395
on r0_d2 inside 4 disk container, returns
b33395
mdadm: Need 2 spares to avoid degraded array, only have 0.
b33395
b33395
Signed-off-by: Mateusz Kusiak <mateusz.kusiak@intel.com>
b33395
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
b33395
---
b33395
 Grow.c | 8 ++++++++
b33395
 1 file changed, 8 insertions(+)
b33395
b33395
diff --git a/Grow.c b/Grow.c
b33395
index 8a242b0f..f6efbc48 100644
b33395
--- a/Grow.c
b33395
+++ b/Grow.c
b33395
@@ -1892,6 +1892,14 @@ int Grow_reshape(char *devname, int fd,
b33395
 
b33395
 		if (retval) {
b33395
 			pr_err("Cannot read superblock for %s\n", devname);
b33395
+			close(cfd);
b33395
+			free(subarray);
b33395
+			return 1;
b33395
+		}
b33395
+
b33395
+		if (s->raiddisks && subarray) {
b33395
+			pr_err("--raid-devices operation can be performed on a container only\n");
b33395
+			close(cfd);
b33395
 			free(subarray);
b33395
 			return 1;
b33395
 		}
b33395
-- 
2ad819
2.38.1
b33395