Na}{

File Content: `65-md-incremental.rules`

# This file causes block devices with Linux RAID (mdadm) signatures to
# automatically cause mdadm to be run.
# See udev(8) for syntax

# 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}=="?*", GOTO="md_end"

# We process add events on block devices (since they are ready as soon as
# they are added to the system), but we must process change events as well
# on any dm devices (like LUKS partitions or LVM logical volumes) and on
# md devices because both of these first get added, then get brought live
# and trigger a change event.  The reason we don't process change events
# on bare hard disks is because if you stop all arrays on a disk, then
# run fdisk on the disk to change the partitions, when fdisk exits it
# triggers a change event, and we want to wait until all the fdisks on
# all member disks are done before we do anything.  Unfortunately, we have
# no way of knowing that, so we just have to let those arrays be brought
# up manually after fdisk has been run on all of the disks.

# First, process all add events (md and dm devices will not really do
# anything here, just regular disks, and this also won't get any imsm
# array members either)
SUBSYSTEM=="block", ACTION=="add", ENV{ID_FS_TYPE}=="linux_raid_member", \
	IMPORT{program}="/sbin/mdadm -I $env{DEVNAME} --export $devnode --offroot ${DEVLINKS}"
SUBSYSTEM=="block", ACTION=="add", ENV{ID_FS_TYPE}=="linux_raid_member", \
	ENV{MD_STARTED}=="*unsafe*", ENV{MD_FOREIGN}=="no", ENV{SYSTEMD_WANTS}+="mdadm-last-resort@$env{MD_DEVICE}.timer"

# Next, check to make sure the BIOS raid stuff wasn't turned off via cmdline
IMPORT{cmdline}="noiswmd"
IMPORT{cmdline}="nodmraid"
ENV{noiswmd}=="?*", GOTO="md_imsm_inc_end"
ENV{nodmraid}=="?*", GOTO="md_imsm_inc_end"
SUBSYSTEM=="block", ACTION=="add", ENV{ID_FS_TYPE}=="isw_raid_member", \
	RUN+="/sbin/mdadm -I $env{DEVNAME}"
LABEL="md_imsm_inc_end"

SUBSYSTEM=="block", ACTION=="remove", ENV{ID_PATH}=="?*", \
	RUN+="/sbin/mdadm -If $name --path $env{ID_PATH}"
SUBSYSTEM=="block", ACTION=="remove", ENV{ID_PATH}!="?*", \
	RUN+="/sbin/mdadm -If $name"

# Next make sure that this isn't a dm device we should skip for some reason
ENV{DM_UDEV_RULES_VSN}!="?*", GOTO="dm_change_end"
ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", GOTO="dm_change_end"
ENV{DM_SUSPENDED}=="1", GOTO="dm_change_end"
KERNEL=="dm-*", SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="linux_raid_member", \
	ACTION=="change", RUN+="/sbin/mdadm -I $env{DEVNAME}"
LABEL="dm_change_end"

# Finally catch any nested md raid arrays.  If we brought up an md raid
# array that's part of another md raid array, it won't be ready to be used
# until the change event that occurs when it becomes live
KERNEL=="md*", SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="linux_raid_member", \
	ACTION=="change", RUN+="/sbin/mdadm -I $env{DEVNAME}"

LABEL="md_end"

Name	Size	Permission
01-md-raid-creating.rules	321 bytes	0644
10-dm.rules	7266 bytes	0444
11-dm-lvm.rules	2454 bytes	0444
13-dm-disk.rules	1794 bytes	0444
40-redhat-disable-dell-ir-camera.rules	135 bytes	0644
40-redhat-disable-lenovo-ir-camera.rules	496 bytes	0644
40-redhat.rules	1786 bytes	0644
42-usb-hid-pm.rules	2207 bytes	0644
50-udev-default.rules	3284 bytes	0644
60-alias-kmsg.rules	357 bytes	0644
60-cdrom_id.rules	910 bytes	0644
60-drm.rules	153 bytes	0644
60-evdev.rules	532 bytes	0644
60-keyboard.rules	821 bytes	0644
60-net.rules	129 bytes	0644
60-persistent-alsa.rules	616 bytes	0644
60-persistent-input.rules	2464 bytes	0644
60-persistent-serial.rules	947 bytes	0644
60-persistent-storage-tape.rules	1563 bytes	0644
60-persistent-storage.rules	7272 bytes	0644
60-persistent-v4l.rules	769 bytes	0644
60-raw.rules	326 bytes	0644
61-accelerometer.rules	166 bytes	0644
63-md-raid-arrays.rules	2377 bytes	0644
64-btrfs-dm.rules	387 bytes	0644
64-btrfs.rules	418 bytes	0644
65-md-incremental.rules	2992 bytes	0644
69-dm-lvm-metad.rules	6375 bytes	0444
69-md-clustered-confirm-device.rules	858 bytes	0644
70-mouse.rules	734 bytes	0644
70-power-switch.rules	706 bytes	0644
70-touchpad.rules	345 bytes	0644
70-uaccess.rules	2591 bytes	0644
71-biosdevname.rules	1086 bytes	0644
71-seat.rules	2360 bytes	0644
73-idrac.rules	316 bytes	0644
73-seat-late.rules	596 bytes	0644
75-net-description.rules	452 bytes	0644
75-probe_mtd.rules	174 bytes	0644
75-tty-description.rules	426 bytes	0644
76-phys-port-name.rules	473 bytes	0644
78-sound-card.rules	4400 bytes	0644
80-drivers.rules	618 bytes	0644
80-net-name-slot.rules	491 bytes	0644
80-net-setup-link.rules	292 bytes	0644
81-kvm-rhel.rules	92 bytes	0644
90-iprutils.rules	70 bytes	0644
90-vconsole.rules	441 bytes	0644
91-drm-modeset.rules	56 bytes	0644
95-dm-notify.rules	483 bytes	0444
95-udev-late.rules	155 bytes	0644
98-kexec.rules	695 bytes	0644
99-systemd.rules	4072 bytes	0644

File Content: 65-md-incremental.rules

File Content: `65-md-incremental.rules`