72c1204567
Now mdcheck service can't be run successfully. We need to put mdcheck in to the right place (/usr/share/mdadm/mdcheck) and it needs to remove the dependency of mdadm_env.sh which is fixed in patch 76c224c6c. And there is a history problem. It needed KillMode=none before, so it removed the upstream patch 52c67fcdd. Now this problem has been fixed, so we can do the backport more easilly now. We don't need to remove the upstream patch here again. It adds a rhel only feature too for transient failure. Resolves: rhbz#2159923, rhbz#2150865, rhbz#2124071, rhbz#2203859 Signed-off-by: Xiao Ni <xni@redhat.com>
28 lines
895 B
Plaintext
28 lines
895 B
Plaintext
#
|
||
# Enable/Disable - default is Disabled
|
||
# to disable this rule, GOTO="md_end" should be the first active command.
|
||
# to enable this rule, Comment out GOTO="md_end".
|
||
GOTO="md_end"
|
||
|
||
# Required: MD arrays must have a bitmap for transient devices to
|
||
# be added back in the array.
|
||
# mdadm -CR /dev/md0 -l1 -n2 /dev/sd[ab] –bitmap=internal
|
||
|
||
# Don't process any events if anaconda is running as anaconda brings up
|
||
# raid devices manually
|
||
ENV{ANACONDA}=="?*", GOTO="md_end"
|
||
|
||
# Also don't process disks that are slated to be a multipath device
|
||
ENV{DM_MULTIPATH_DEVICE_PATH}=="1", GOTO="md_end"
|
||
|
||
# We process add events on block devices (since they are ready as soon as
|
||
# they are added to the system)
|
||
|
||
ACTION!="add", GOTO="md_end"
|
||
ENV{ID_FS_TYPE}!="linux_raid_member", GOTO="md_end"
|
||
SUBSYSTEM=="block", RUN{program}+="/usr/sbin/md-auto-readd.sh $devnode"
|
||
|
||
#
|
||
# Land here to exit cleanly
|
||
LABEL="md_end"
|