Blame SOURCES/0074-RHBZ-1056976-dm-mpath-rules.patch

4ae388
---
4ae388
 multipath/11-dm-mpath.rules |   34 ++++++++++++++++++++++++++++++++++
4ae388
 multipath/Makefile          |    2 ++
4ae388
 2 files changed, 36 insertions(+)
4ae388
4ae388
Index: multipath-tools-130222/multipath/11-dm-mpath.rules
4ae388
===================================================================
4ae388
--- /dev/null
4ae388
+++ multipath-tools-130222/multipath/11-dm-mpath.rules
4ae388
@@ -0,0 +1,34 @@
4ae388
+ACTION!="add|change", GOTO="mpath_end"
4ae388
+ENV{DM_UDEV_RULES_VSN}!="?*", GOTO="mpath_end"
4ae388
+ENV{DM_UUID}!="mpath-?*", GOTO="mpath_end"
4ae388
+
4ae388
+# Do not initiate scanning if no path is available,
4ae388
+# otherwise there would be a hang or IO error on access.
4ae388
+# We'd like to avoid this, especially within udev processing.
4ae388
+ENV{DM_NR_VALID_PATHS}!="?*", IMPORT{db}="DM_NR_VALID_PATHS"
4ae388
+ENV{DM_NR_VALID_PATHS}=="0", ENV{DM_NOSCAN}="1"
4ae388
+
4ae388
+# Also skip all foreign rules if no path is available.
4ae388
+# Remember the original value of DM_DISABLE_OTHER_RULES_FLAG
4ae388
+# and restore it back once we have at least one path available.
4ae388
+IMPORT{db}="DM_DISABLE_OTHER_RULES_FLAG_OLD"
4ae388
+ENV{DM_ACTION}=="PATH_FAILED",\
4ae388
+	ENV{DM_NR_VALID_PATHS}=="0",\
4ae388
+	ENV{DM_DISABLE_OTHER_RULES_FLAG_OLD}=="",\
4ae388
+	ENV{DM_DISABLE_OTHER_RULES_FLAG_OLD}="$env{DM_UDEV_DISABLE_OTHER_RULES_FLAG}",\
4ae388
+	ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}="1"
4ae388
+ENV{DM_ACTION}=="PATH_REINSTATED",\
4ae388
+	ENV{DM_NR_VALID_PATHS}=="1",\
4ae388
+	ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}="$env{DM_DISABLE_OTHER_RULES_FLAG_OLD}",\
4ae388
+	ENV{DM_DISABLE_OTHER_RULES_FLAG_OLD}="",\
4ae388
+	ENV{DM_ACTIVATION}="1"
4ae388
+
4ae388
+# DM_SUBSYSTEM_UDEV_FLAG0 is the "RELOAD" flag for multipath subsystem.
4ae388
+# Drop the DM_ACTIVATION flag here as mpath reloads tables if any of its
4ae388
+# paths are lost/recovered. For any stack above the mpath device, this is not
4ae388
+# something that should be reacted upon since it would be useless extra work.
4ae388
+# It's exactly mpath's job to provide *seamless* device access to any of the
4ae388
+# paths that are available underneath.
4ae388
+ENV{DM_SUBSYSTEM_UDEV_FLAG0}=="1", ENV{DM_ACTIVATION}="0"
4ae388
+
4ae388
+LABEL="mpath_end"
4ae388
Index: multipath-tools-130222/multipath/Makefile
4ae388
===================================================================
4ae388
--- multipath-tools-130222.orig/multipath/Makefile
4ae388
+++ multipath-tools-130222/multipath/Makefile
4ae388
@@ -25,6 +25,7 @@ install:
4ae388
 	$(INSTALL_PROGRAM) -m 755 mpathconf $(DESTDIR)$(bindir)/
4ae388
 	$(INSTALL_PROGRAM) -d $(DESTDIR)/usr/lib/udev/rules.d
4ae388
 	$(INSTALL_PROGRAM) -m 644 multipath.rules $(DESTDIR)/usr/lib/udev/rules.d/62-multipath.rules
4ae388
+	$(INSTALL_PROGRAM) -m 644 11-dm-mpath.rules $(DESTDIR)/usr/lib/udev/rules.d/11-dm-mpath.rules
4ae388
 	$(INSTALL_PROGRAM) -d $(DESTDIR)$(mandir)
4ae388
 	$(INSTALL_PROGRAM) -m 644 $(EXEC).8.gz $(DESTDIR)$(mandir)
4ae388
 	$(INSTALL_PROGRAM) -d $(DESTDIR)$(man5dir)
4ae388
@@ -33,6 +34,7 @@ install:
4ae388
 
4ae388
 uninstall:
4ae388
 	rm $(DESTDIR)/usr/lib/udev/rules.d/62-multipath.rules
4ae388
+	rm $(DESTDIR)/usr/lib/udev/rules.d/11-dm-mpath.rules
4ae388
 	rm $(DESTDIR)$(bindir)/$(EXEC)
4ae388
 	rm $(DESTDIR)$(bindir)/mpathconf
4ae388
 	rm $(DESTDIR)$(mandir)/$(EXEC).8.gz