The "SYSTEMD_READY=0" will cause automatic unmount of mountpoint that is on top of such DM device. It's even more problematic if this is used with multipath which sets DM_UDEV_DISABLE_OTHER_RULES_FLAG in case we have a CHANGE event that comes after DM multipath device reload when one of the paths is down or up (see also bug #1310022).
This rule may be problematic:
SUBSYSTEM=="block", KERNEL!="ram*", ENV{DM_ UDEV_DISABLE_ OTHER_RULES_ FLAG}== "1", ENV{SYSTEMD_ READY}= "0"
The "SYSTEMD_READY=0" will cause automatic unmount of mountpoint that is on top of such DM device. It's even more problematic if this is used with multipath which sets DM_UDEV_ DISABLE_ OTHER_RULES_ FLAG in case we have a CHANGE event that comes after DM multipath device reload when one of the paths is down or up (see also bug #1310022).