From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001 From: Martin Wilck Date: Wed, 17 Mar 2021 17:30:54 +0100 Subject: [PATCH] 11-dm-mpath.rules: run "multipath -U" with -v1 In cases where some path devices are temporarily unavailable (e.g. failover), high amounts of error messages such as these are seen: Feb 27 08:02:03 ictm1608s02h1 multipath[1420]: get_udev_device: failed to look up 65:224 with type 1 Feb 27 08:02:03 ictm1608s02h1 multipath[1420]: 3600a098000aada210000f1625de51ed9: discarding non-existing path 65:224 This is because every invocation of "multipath -U" prints these messages at the default log level (-v2). In the case of "multipath -U", these messages aren't important, and in failover situations, "multipath -U" is run pretty often, spamming the log with many similar messages. Generally reducing the log level of these messages would be wrong, because they are important for multipathd's operation, to verify that multipathd does the right thing when discovering a discrepancy between the dm state and the devices present in the system. Therefore, just decrease the verbosity with which we invoke "multipath -U" in the udev rules. Reviewed-by: Benjamin Marzinski Signed-off-by: Benjamin Marzinski --- multipath/11-dm-mpath.rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/multipath/11-dm-mpath.rules b/multipath/11-dm-mpath.rules index cd522e8c..d191ae8d 100644 --- a/multipath/11-dm-mpath.rules +++ b/multipath/11-dm-mpath.rules @@ -32,7 +32,7 @@ ACTION=="add", ENV{.MPATH_DEVICE_READY_OLD}=="1", GOTO="paths_ok" # Check the map state directly with multipath -U. # This doesn't attempt I/O on the device. -PROGRAM=="$env{MPATH_SBIN_PATH}/multipath -U %k", GOTO="paths_ok" +PROGRAM=="$env{MPATH_SBIN_PATH}/multipath -U -v1 %k", GOTO="paths_ok" ENV{MPATH_DEVICE_READY}="0", GOTO="mpath_action" LABEL="paths_ok"