Blame SOURCES/lvm2-remove-mpath-device-handling-from-udev-rules.patch

5f1a1f
 udev/10-dm.rules.in | 4 ----
5f1a1f
 1 file changed, 4 deletions(-)
5f1a1f
5f1a1f
diff --git a/udev/10-dm.rules.in b/udev/10-dm.rules.in
5f1a1f
index 2755530..8d7a8ca 100644
5f1a1f
--- a/udev/10-dm.rules.in
5f1a1f
+++ b/udev/10-dm.rules.in
5f1a1f
@@ -120,10 +120,6 @@ ENV{DM_UDEV_RULES_VSN}="2"
5f1a1f
 
5f1a1f
 ENV{DM_UDEV_DISABLE_DM_RULES_FLAG}!="1", ENV{DM_NAME}=="?*", SYMLINK+="(DM_DIR)/$env{DM_NAME}"
5f1a1f
 
5f1a1f
-# We have to ignore further rule application for inappropriate events
5f1a1f
-# and devices. But still send the notification if cookie exists.
5f1a1f
-ENV{DM_UUID}=="mpath-?*", ENV{DM_ACTION}=="PATH_FAILED", GOTO="dm_disable"
5f1a1f
-
5f1a1f
 # Avoid processing and scanning a DM device in the other (foreign)
5f1a1f
 # rules if it is in suspended state. However, we still keep 'disk'
5f1a1f
 # and 'DM subsystem' related rules enabled in this case.