Blame SOURCES/mdadm-udev.patch
|
 |
c3a0e9 |
--- mdadm/udev-md-raid-assembly.rules.orig 2022-10-25 08:34:58.137936285 +0800
|
|
|
c3a0e9 |
+++ mdadm/udev-md-raid-assembly.rules 2022-10-25 09:28:23.453154190 +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
|
|
|
c3a0e9 |
@@ -28,6 +31,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.
|
|
|
c3a0e9 |
+# 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 |
+
|
|
|
c3a0e9 |
# remember you can limit what gets auto/incrementally assembled by
|
|
|
c3a0e9 |
# mdadm.conf(5)'s 'AUTO' and selectively whitelist using 'ARRAY'
|
|
|
c3a0e9 |
ACTION!="remove", IMPORT{program}="BINDIR/mdadm --incremental --export $devnode --offroot $env{DEVLINKS}"
|