mrc0mmand / rpms / lvm2

Forked from rpms/lvm2 2 years ago
Clone

Blame SOURCES/lvm2-2_02_178-pvmove-drop-misleading-pvmove-restriction-for-cluste.patch

f0aa83
From 00277d60e98409e493f6208f7f541f7b85ace91f Mon Sep 17 00:00:00 2001
f0aa83
From: Zdenek Kabelac <zkabelac@redhat.com>
f0aa83
Date: Thu, 11 Jan 2018 16:15:16 +0100
f0aa83
Subject: [PATCH 16/25] pvmove: drop misleading pvmove restriction for cluster
f0aa83
f0aa83
pvmove handles properly locked LVs in cluster and this extra check
f0aa83
actually cause misbehavior as some LVs were silently skipped from
f0aa83
operation scope.
f0aa83
f0aa83
(cherry picked from commit 02621cffb0d5ff72adb8770e26c1b4adb95bd0d9)
f0aa83
---
f0aa83
 tools/pvmove.c | 10 ----------
f0aa83
 1 file changed, 10 deletions(-)
f0aa83
f0aa83
diff --git a/tools/pvmove.c b/tools/pvmove.c
f0aa83
index 9bbe12b..c5d7e52 100644
f0aa83
--- a/tools/pvmove.c
f0aa83
+++ b/tools/pvmove.c
f0aa83
@@ -371,16 +371,6 @@ static struct logical_volume *_set_up_pvmove_lv(struct cmd_context *cmd,
f0aa83
 		if (lv_name && strcmp(lv->name, top_level_lv_name(vg, lv_name)))
f0aa83
 			continue;
f0aa83
 
f0aa83
-		/*
f0aa83
-		 * RAID, thin and snapshot-related LVs are not
f0aa83
-		 * processed in a cluster, so we don't have to
f0aa83
-		 * worry about avoiding certain PVs in that context.
f0aa83
-		 *
f0aa83
-		 * Allow clustered mirror, but not raid mirror.
f0aa83
-		 */
f0aa83
-		if (vg_is_clustered(vg) && !lv_is_mirror_type(lv))
f0aa83
-			continue;
f0aa83
-
f0aa83
 		if (!lv_is_on_pvs(lv, source_pvl))
f0aa83
 			continue;
f0aa83
 
f0aa83
-- 
f0aa83
1.8.3.1
f0aa83