/usr/lib/udev/rules.d
NameSizeModeActions
01-md-raid-creating.rules3210644editdlrm
40-vm-hotadd.rules6550644editdlrm
50-apport.rules1650644editdlrm
50-firmware.rules2100644editdlrm
50-udev-default.rules39310644editdlrm
55-dm.rules72740644editdlrm
55-scsi-sg3_id.rules47810644editdlrm
56-dm-mpath.rules45300644editdlrm
56-dm-parts.rules14420644editdlrm
56-lvm.rules24200644editdlrm
58-scsi-sg3_symlink.rules28850644editdlrm
60-autosuspend-chromiumos.rules85950644editdlrm
60-block.rules7030644editdlrm
60-cdrom_id.rules10710644editdlrm
60-drm.rules4130644editdlrm
60-evdev.rules9900644editdlrm
60-fido-id.rules3940644editdlrm
60-input-id.rules2820644editdlrm
60-multipath.rules38710644editdlrm
60-open-vm-tools.rules2500644editdlrm
60-persistent-alsa.rules6160644editdlrm
60-persistent-input.rules27100644editdlrm
60-persistent-storage-dm.rules17940644editdlrm
60-persistent-storage-tape.rules21350644editdlrm
60-persistent-storage.rules77820644editdlrm
60-persistent-v4l.rules7690644editdlrm
60-sensor.rules7360644editdlrm
60-serial.rules11900644editdlrm
60-tpm-udev.rules2110644editdlrm
61-autosuspend-manual.rules5650644editdlrm
61-persistent-storage-android.rules4560644editdlrm
63-md-raid-arrays.rules21300644editdlrm
64-btrfs-dm.rules3870644editdlrm
64-btrfs.rules6120644editdlrm
64-md-raid-assembly.rules14440644editdlrm
66-azure-ephemeral.rules19510644editdlrm
66-snapd-autoimport.rules1900644editdlrm
68-del-part-nodes.rules11420644editdlrm
69-bcache.rules10440644editdlrm
69-lvm-metad.rules66050644editdlrm
69-md-clustered-confirm-device.rules8460644editdlrm
70-iscsi-disk.rules2530644editdlrm
70-iscsi-network-interface.rules2260644editdlrm
70-joystick.rules4320644editdlrm
70-mouse.rules7340644editdlrm
70-power-switch.rules5680644editdlrm
70-touchpad.rules4730644editdlrm
70-uaccess.rules28000644editdlrm
71-power-switch-proliant.rules4610644editdlrm
71-seat.rules37820644editdlrm
73-seat-late.rules6360644editdlrm
73-special-net-names.rules9690644editdlrm
75-net-description.rules4520644editdlrm
75-probe_mtd.rules1740644editdlrm
78-graphics-card.rules9650644editdlrm
78-sound-card.rules48160644editdlrm
80-debian-compat.rules13750644editdlrm
80-drivers.rules6150644editdlrm
80-net-setup-link.rules2950644editdlrm
81-net-dhcp.rules5280644editdlrm
85-hdparm.rules820644editdlrm
90-bolt.rules3500644editdlrm
90-console-setup.rules2650644editdlrm
90-fwupd-devices.rules14720644editdlrm
95-dm-notify.rules4790644editdlrm
95-kpartx.rules13350644editdlrm
96-e2scrub.rules1710644editdlrm
99-systemd.rules47130644editdlrm
99-vmware-scsi-udev.rules4330644editdlrm
Edit: /usr/lib/udev/rules.d/69-lvm-metad.rules (6605B)
# Copyright (C) 2012 Red Hat, Inc. All rights reserved. # # This file is part of LVM2. # Udev rules for LVM. # # Scan all block devices having a PV label for LVM metadata. # Store this information in LVMetaD (the LVM metadata daemon) and maintain LVM # metadata state for improved performance by avoiding further scans while # running subsequent LVM commands or while using lvm2app library. # Also, notify LVMetaD about any relevant block device removal. # # This rule is essential for having the information in LVMetaD up-to-date. # It also requires blkid to be called on block devices before so only devices # used as LVM PVs are processed (ID_FS_TYPE="LVM2_member" or "LVM1_member"). SUBSYSTEM!="block", GOTO="lvm_end" ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", GOTO="lvm_end" # XXX: Properly call blkid on md devices. Workaround for #793631 KERNEL!="md[0-9]*", GOTO="next" IMPORT{builtin}="blkid" LABEL="next" # If the PV label got lost, inform lvmetad immediately. # Detect the lost PV label by comparing previous ID_FS_TYPE value with current one. ENV{.ID_FS_TYPE_NEW}="$env{ID_FS_TYPE}" IMPORT{db}="ID_FS_TYPE" ENV{ID_FS_TYPE}=="LVM2_member|LVM1_member", ENV{.ID_FS_TYPE_NEW}!="LVM2_member|LVM1_member", ENV{LVM_PV_GONE}="1" ENV{ID_FS_TYPE}="$env{.ID_FS_TYPE_NEW}" ENV{LVM_PV_GONE}=="1", GOTO="lvm_scan" # Only process devices already marked as a PV - this requires blkid to be called before. ENV{ID_FS_TYPE}!="LVM2_member|LVM1_member", GOTO="lvm_end" ENV{DM_MULTIPATH_DEVICE_PATH}=="1", GOTO="lvm_end" # Inform lvmetad about any PV that is gone. ACTION=="remove", GOTO="lvm_scan" # Create /dev/disk/by-id/lvm-pv-uuid- symlink for each PV ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-id/lvm-pv-uuid-$env{ID_FS_UUID_ENC}" # If the PV is a special device listed below, scan only if the device is # properly activated. These devices are not usable after an ADD event, # but they require an extra setup and they are ready after a CHANGE event. # Also support coldplugging with ADD event but only if the device is already # properly activated. # This logic should be eventually moved to rules where those particular # devices are processed primarily (MD and loop). # DM device: KERNEL!="dm-[0-9]*", GOTO="next" ENV{DM_UDEV_PRIMARY_SOURCE_FLAG}=="1", ENV{DM_ACTIVATION}=="1", GOTO="lvm_scan" GOTO="lvm_end" # MD device: LABEL="next" KERNEL!="md[0-9]*", GOTO="next" IMPORT{db}="LVM_MD_PV_ACTIVATED" ACTION=="add", ENV{LVM_MD_PV_ACTIVATED}=="1", GOTO="lvm_scan" ACTION=="change", ENV{LVM_MD_PV_ACTIVATED}!="1", ENV{LVM_MD_PV_ACTIVATED}="1", GOTO="lvm_scan" ACTION=="add", KERNEL=="md[0-9]*p[0-9]*", GOTO="lvm_scan" ENV{LVM_MD_PV_ACTIVATED}!="1", ENV{SYSTEMD_READY}="0" GOTO="lvm_end" # Loop device: LABEL="next" KERNEL!="loop[0-9]*", GOTO="next" ACTION=="add", ENV{LVM_LOOP_PV_ACTIVATED}=="1", GOTO="lvm_scan" ACTION=="change", ENV{LVM_LOOP_PV_ACTIVATED}!="1", ENV{LVM_LOOP_PV_ACTIVATED}="1", GOTO="lvm_scan" ENV{LVM_LOOP_PV_ACTIVATED}!="1", ENV{SYSTEMD_READY}="0" GOTO="lvm_end" # If the PV is not a special device listed above, scan only if necessary. # For "direct_pvscan" mode (see below), this means run rules only an ADD events. # For "systemd_background" mode, systemd takes care of this by activating # the lvm2-pvscan@.service only once. LABEL="next" TEST!="/run/systemd/system", ACTION!="add", GOTO="lvm_end" TEST=="/run/systemd/system", ACTION!="add|change", GOTO="lvm_end" LABEL="lvm_scan" ENV{SYSTEMD_READY}="1" # The method for invoking pvscan is selected at build time with the option # --(enable|disable)-udev-systemd-background-jobs to "configure". # On modern distributions with recent systemd, it's "systemd_background"; # on others, "direct_pvscan". TEST!="/run/systemd/system", GOTO="direct_pvscan" TEST=="/run/systemd/system", GOTO="systemd_background" LABEL="systemd_background" # The table below summarises the situations in which we reach the LABEL="lvm_scan" # in the "systemd_background" case. # Marked by X, X* means only if the special dev is properly set up. # The artificial ADD is supported for coldplugging. We avoid running the pvscan # on artificial CHANGE so there's no unexpected autoactivation when WATCH rule fires. # N.B. MD and loop never actually reaches lvm_scan on REMOVE as the PV label is gone # within a CHANGE event (these are caught by the "LVM_PV_GONE" rule at the beginning). # # In this case, we simply set up the dependency between the device and the pvscan # job using SYSTEMD_ALIAS (which sets up a simplified device identifier that # allows using "BindsTo" in the sytemd unit file) and SYSTEMD_WANTS (which tells # systemd to start the pvscan job once the device is ready). # We need to set these variables for both "add" and "change" events, otherwise # systemd may loose information about the device/unit dependencies. # # | real ADD | real CHANGE | artificial ADD | artificial CHANGE | REMOVE # ============================================================================= # DM | | X | X* | | X # MD | | X | X* | | # loop | | X | X* | | # other | X | X | X | | X ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/usr/bin/systemd-run /sbin/lvm pvscan --cache $major:$minor", GOTO="lvm_end" ENV{SYSTEMD_ALIAS}="/dev/block/$major:$minor" ENV{SYSTEMD_WANTS}+="lvm2-pvscan@$major:$minor.service" GOTO="lvm_end" LABEL="direct_pvscan" # The table below summarises the situations in which we reach the LABEL="lvm_scan" # for the "direct_pvscan" case. # Marked by X, X* means only if the special dev is properly set up. # The artificial ADD is supported for coldplugging. We avoid running the pvscan # on artificial CHANGE so there's no unexpected autoactivation when WATCH rule fires. # # In this case, we need to make sure that pvscan is not invoked spuriously, therefore # we invoke it only for "add" events for "other" devices. # # | real ADD | real CHANGE | artificial ADD | artificial CHANGE | REMOVE # ============================================================================= # DM | | X | X* | | X # MD | | X | X* | | # loop | | X | X* | | # other | X | | X | | X RUN+="/sbin/lvm pvscan --cache --activate ay --major $major --minor $minor", ENV{LVM_SCANNED}="1" LABEL="lvm_end"