summaryrefslogtreecommitdiff
path: root/rules/99-systemd.rules.in
diff options
context:
space:
mode:
authorLukáš Nykrýn <lnykryn@redhat.com>2016-04-12 07:44:28 +0200
committerMartin Pitt <martin.pitt@ubuntu.com>2016-04-12 07:44:28 +0200
commit35a6750d9e26b26b423fbe815bead7d750210d8d (patch)
tree65d5670c9d936f0c1c700e3b03e26662b8502ea1 /rules/99-systemd.rules.in
parentdbab702a2a2ba942d75f9682e2ab11f9b55df683 (diff)
rules: set SYSTEMD_READY=0 on DM_UDEV_DISABLE_OTHER_RULES_FLAG=1 only with ADD event (#2747)
The "SYSTEMD_READY=0" will cause automatic unmount of mountpoint that is on top of such DM device if this is used with multipath which sets DM_UDEV_DISABLE_OTHER_RULES_FLAG in case we have a CHANGE event thatcomes after DM multipath device reload when one of the paths is down or up. See https://bugzilla.redhat.com/show_bug.cgi?id=1312011
Diffstat (limited to 'rules/99-systemd.rules.in')
-rw-r--r--rules/99-systemd.rules.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/rules/99-systemd.rules.in b/rules/99-systemd.rules.in
index 5c2cda51ec..0ac4f6af7e 100644
--- a/rules/99-systemd.rules.in
+++ b/rules/99-systemd.rules.in
@@ -11,7 +11,7 @@ SUBSYSTEM=="tty", KERNEL=="tty[a-zA-Z]*|hvc*|xvc*|hvsi*|ttysclp*|sclp_line*|3270
KERNEL=="vport*", TAG+="systemd"
SUBSYSTEM=="block", TAG+="systemd"
-SUBSYSTEM=="block", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"
+SUBSYSTEM=="block", ACTION=="add", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"
# Ignore encrypted devices with no identified superblock on it, since
# we are probably still calling mke2fs or mkswap on it.