Blame SOURCES/mdadm-udev.patch
|
 |
91179e |
--- mdadm/udev-md-raid-assembly.rules.orig 2023-01-06 16:37:03.780756100 +0800
|
|
|
91179e |
+++ mdadm/udev-md-raid-assembly.rules 2023-01-06 17:04:09.536159980 +0800
|
|
|
c3a0e9 |
@@ -5,6 +5,9 @@
|
|
|
c3a0e9 |
ENV{ANACONDA}=="?*", GOTO="md_inc_end"
|
|
|
c3a0e9 |
# assemble md arrays
|
|
|
c3a0e9 |
|
|
|
c3a0e9 |
+# Also don't process disks that are slated to be a multipath device
|
|
|
c3a0e9 |
+ENV{DM_MULTIPATH_DEVICE_PATH}=="1", GOTO="md_inc_end"
|
|
|
c3a0e9 |
+
|
|
|
c3a0e9 |
SUBSYSTEM!="block", GOTO="md_inc_end"
|
|
|
c3a0e9 |
|
|
|
c3a0e9 |
# skip non-initialized devices
|
|
|
91179e |
@@ -33,6 +36,13 @@
|
|
|
c3a0e9 |
|
|
|
c3a0e9 |
LABEL="md_inc"
|
|
|
c3a0e9 |
|
|
|
c3a0e9 |
+# Make sure we don't handle dm devices when some limits are set.
|
|
|
c3a0e9 |
+# And linux_raid_member only be set when change/remove event happen.
|
|
|
91179e |
+# So we don't need to consider add event here.
|
|
|
c3a0e9 |
+KERNEL=="dm-*", ENV{DM_UDEV_RULES_VSN}!="?*", GOTO="md_inc_end"
|
|
|
c3a0e9 |
+KERNEL=="dm-*", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", GOTO="md_inc_end"
|
|
|
c3a0e9 |
+KERNEL=="dm-*", ENV{DM_SUSPENDED}=="1", GOTO="md_inc_end"
|
|
|
c3a0e9 |
+
|
|
|
91179e |
# Bare disks are ready when add event happens, the raid can be assembled.
|
|
|
91179e |
ACTION=="change", KERNEL!="dm-*|md*", GOTO="md_inc_end"
|
|
|
91179e |
|