Blame SOURCES/rear-bz1993296.patch

52df35
From 4233fe30b315737ac8c4d857e2b04e021c2e2886 Mon Sep 17 00:00:00 2001
52df35
From: Pavel Cahyna <pcahyna@redhat.com>
52df35
Date: Mon, 16 Aug 2021 10:10:38 +0300
52df35
Subject: [PATCH] Revert the main part of PR #2299
52df35
52df35
multipath -l is very slow with many multipath devices. As it will be
52df35
called for every multipath device, it leads to quadratic time complexity
52df35
in the number of multipath devices. For thousands of devices, ReaR can
52df35
take hours to scan and exclude them. We therefore have to comment
52df35
multipath -l out, as it is a huge performance regression, and find
52df35
another solution to bug #2298.
52df35
---
52df35
 usr/share/rear/lib/layout-functions.sh | 5 ++++-
52df35
 1 file changed, 4 insertions(+), 1 deletion(-)
52df35
52df35
diff --git a/usr/share/rear/lib/layout-functions.sh b/usr/share/rear/lib/layout-functions.sh
52df35
index cdd81a14..8c8be74b 100644
52df35
--- a/usr/share/rear/lib/layout-functions.sh
52df35
+++ b/usr/share/rear/lib/layout-functions.sh
52df35
@@ -771,7 +771,10 @@ function is_multipath_path {
52df35
     # so that no "multipath -l" output could clutter the log (the "multipath -l" output is irrelevant here)
52df35
     # in contrast to e.g. test "$( multipath -l )" that would falsely succeed with blank output
52df35
     # and the output would appear in the log in 'set -x' debugscript mode:
52df35
-    multipath -l | grep -q '[[:alnum:]]' || return 1
52df35
+    #
52df35
+    # Unfortunately, multipat -l is quite slow with many multipath devices
52df35
+    # and becomes a performance bottleneck, so we must comment it out for now.
52df35
+    #multipath -l | grep -q '[[:alnum:]]' || return 1
52df35
     # Check if a block device should be a path in a multipath device:
52df35
     multipath -c /dev/$1 &>/dev/null
52df35
 }
52df35
-- 
52df35
2.26.3
52df35