shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00
Code Releases Activity
038760da4f
lvm2/udev/11-dm-lvm.rules.in

54 lines
2.1 KiB
Plaintext
Raw Normal View History

add copyright lines
2009-10-27 01:42:07 +03:00
# Copyright (C) 2009 Red Hat, Inc. All rights reserved.
#
# This file is part of LVM2.
Add default udev rules. Update dm-ioctl.h comments.
2009-08-03 22:44:54 +04:00
# Udev rules for LVM.
#
# These rules create symlinks for LVM logical volumes in
# /dev/VG directory (VG is an actual VG name). Some udev
# environment variables are set (they can be used in later
# rules as well):
# DM_LV_NAME - logical volume name
# DM_VG_NAME - volume group name
# DM_LV_LAYER - logical volume layer (blank if not set)
Use udev flags in the rules and cleanup the rules: - remove default permissions set in 95-dm-notify.rules (and add a hint in 12-dm-permissions.rules to set it by the user directly) - add multipath DM_ACTION=="PATH_FAILED" filter - remove unnecessary filters in the headers of the rules (we can simply use DM_UDEV_RULES_VSN instead) - fix symlink priorities in /dev/disk/ (snapshot volumes have low priority for FS UUID symlinks so it will not overwrite symlinks for the origin)
2009-10-22 17:11:33 +04:00
# "add" event is processed on coldplug only!
udev: change action check from ACTION!="add|change" to ACTION=="remove" For DM devices, the add/change/remove can appear as action for genuine udev events. However, there are more action types (bind, unbind, move, online, offline) which never appear as actions for genuine DM udev events, but they can still be synthesized (e.g. by writing "<action>" to "/sys/.../uevent" file or by calling "udevadm trigger --action=<action>"). Let's also process these extra action types so that the udev-related content is not lost completely, keeping all the symlinks and udev db entries just like this was a synthetic udev event with "change" action. Related to https://gitlab.com/lvmteam/lvm2/-/issues/4.
2024-03-07 11:48:49 +03:00
ACTION=="remove", GOTO="lvm_end"
Several changes in udev rules: - add DM_UDEV_RULES_VSN to provide a variable to be checked for in the other rules (e.g. to check that DM rules are actually installed, we can alternate functionality in the other rules based on this information, also we have versioning support for the rules) - set proper sbin path for dmsetup and blkid, /sbin first, then /usr/sbin. This is necessary for anaconda to work properly. - add 'last_rule' for cryptsetup's temporary devices (symlinks in /dev/mapper only)
2009-09-11 20:05:20 +04:00
ENV{DM_UDEV_RULES_VSN}!="?*", GOTO="lvm_end"
Add default udev rules. Update dm-ioctl.h comments.
2009-08-03 22:44:54 +04:00
ENV{DM_UUID}!="LVM-?*", GOTO="lvm_end"
# Use DM name and split it up into its VG/LV/layer constituents.
udev: udev rules cleanup Remove executable path detection in udev rules and use sbindir that is configured, but still provide the original functionality by means of 'configure --enable-udev-rule-exec-detection'. Normally, the exec path for the tools called in udev rules should not differ from the sbindir used, however, there are cases this is necessary. For example different environments could be assembled in a way that these path differ for some reason (distribution installer, initrd ...). This functionality is kept for compatibility only. Any environment moving the binaries around and using different paths should be fixed eventually!
2012-06-22 13:50:02 +04:00
IMPORT{program}="(DM_EXEC)/dmsetup splitname --nameprefixes --noheadings --rows $env{DM_NAME}"
Add default udev rules. Update dm-ioctl.h comments.
2009-08-03 22:44:54 +04:00
udev: add support for "NOSCAN" flag Recognize DM_SUBSYSTEM_UDEV_FLAG0 which for LVM is the "LVM_NOSCAN" flag that causes the scanning to be skipped (mainly blkid) and also directs all the foreign rules to be skipped as well. Important thing here is that the "watch" udev rules is still set as well as the /dev/disk/by-id content created (which does not require any scanning to be done). Also, the flag is dropped on any subsequent event and scanning done...
2013-10-08 15:33:28 +04:00
# DM_SUBSYSTEM_UDEV_FLAG0 is the 'NOSCAN' flag for LVM subsystem.
# This flag is used to temporarily disable selected rules to prevent any
# processing or scanning done on the LVM volume before LVM has any chance
# to zero any stale metadata found within the LV data area. Such stale
# metadata could cause false claim of the LV device, keeping it open etc.
#
11-dm-lvm.rules: don't restore DM_UDEV_DISABLE_OTHER_RULES_FLAG from db DM_UDEV_DISABLE_OTHER_RULES_FLAG is used as the "output" flag of the device-mapper rules, to be consumed by non-dm rules. It is a logical OR of several conditions that might make dm devices inaccessible. 10-dm.rules calculates it for every uevent, whether it's genuine or spurious. DM_SUBSYSTEM_UDEV_FLAG0 is just another flag that needs to be or'd in. We don't need to restore the previous state of DM_UDEV_DISABLE_OTHER_RULES_FLAG. Actually, doing so is wrong if the flag has previously been set because the device was suspended, and the device isn't suspended anymore. Signed-off-by: Martin Wilck <mwilck@suse.com> Reviewed-by: Peter Rajnoha <prajnoha@redhat.com>
2024-03-01 16:45:32 +03:00
# If the NOSCAN flag is present, set DM_UDEV_DISABLE_OTHER_RULES_FLAG
# so those selected rules are surely skipped.
# We don't need to save and restore the previous of DM_UDEV_DISABLE_OTHER_RULES_FLAG,
# that's taken care of in 10-dm.rules.
dm udev rules: don't export and save DM_NOSCAN DM_NOSCAN is not an official API any more and doesn't have to be restored from the udev db. Rename it to .DM_NOSCAN. Signed-off-by: Martin Wilck <mwilck@suse.com> Reviewed-by: Peter Rajnoha <prajnoha@redhat.com>
2024-03-02 01:18:26 +03:00
ENV{DM_SUBSYSTEM_UDEV_FLAG0}=="1", ENV{.DM_NOSCAN}="1", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}="1"
udev: add support for "NOSCAN" flag Recognize DM_SUBSYSTEM_UDEV_FLAG0 which for LVM is the "LVM_NOSCAN" flag that causes the scanning to be skipped (mainly blkid) and also directs all the foreign rules to be skipped as well. Important thing here is that the "watch" udev rules is still set as well as the /dev/disk/by-id content created (which does not require any scanning to be done). Also, the flag is dropped on any subsequent event and scanning done...
2013-10-08 15:33:28 +04:00
Always set environment variables for an LVM2 device in 11-dm-lvm.rules. This way we can still use DM_LV_NAME, DM_VG_NAME and DM_LV_LAYER in all the other rules.
2010-01-07 23:01:55 +03:00
ENV{DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG}=="1", GOTO="lvm_end"
udev: ignore private LVM devs in udev and systemd We automatically ignore these devs, when lvm2 create devs, whoever when lvm2 database is dropped or someone just created these devs with such formated UUID, there is no other informantion then to check DM UUID.
2024-06-03 13:07:07 +03:00
# Ignore private devices - the ones having any suffix in DM_UUID. Both in udev rules and in systemd.
udev: disable suffix handling The idea in the patch 6e6d4c62b for handling -suffix as indication of private device needs to be disabled. Some problematic cases are currently not resolvable and some more thinking is needed. Once fixed, we can revert this patch.
2024-06-26 00:13:54 +03:00
## FIXME resolve -suffix handling
## ENV{DM_UUID}=="LVM-?*-?*", ENV{SYSTEMD_READY}="0", GOTO="lvm_disable"
udev: ignore private LVM devs in udev and systemd We automatically ignore these devs, when lvm2 create devs, whoever when lvm2 database is dropped or someone just created these devs with such formated UUID, there is no other informantion then to check DM UUID.
2024-06-03 13:07:07 +03:00
Several changes to udev support code: - we have these levels when the udev rules are processed: 10-dm.rules --> [11-dm-<subsystem>.rules] --> [12-dm-permissions.rules] --> 13-dm-disk.rules --> [...all the other foreign rules...] --> 95-dm-notify.rules - each level can be disabled now by DM_UDEV_DISABLE_{DM, SUBSYSTEM, DISK, OTHER}_RULES_FLAG - add DM_UDEV_DISABLE_DM_RULES_FLAG to disable 10-dm.rules - add DM_UDEV_DISABLE_OTHER_RULES_FLAG to disable all the other (non-dm) rules. We cutoff these rules by using the 'last_rule', so this one should really be used with great care and in well-founded situations. We use this for lvm's hidden and layer devices now. - add a parameter for add_dev_node, rm_dev_node and rename_dev_node so it's possible to switch on/off udev checks - use DM_UDEV_DISABLE_DM_RULES_FLAG and DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG if there's no cookie set and we have resume, remove and rename ioctl. This could happen when someone uses the libdevmapper that is compiled with udev_sync but the software does not make use of it. This way we can switch off the rules and fallback to libdevmapper node creation so there's no udev/libdevmapper race.
2009-10-26 17:29:33 +03:00
# Do not create symlinks for inappropriate subdevices.
Remove hard-coded rule to skip _mimage devices in 11-dm-lvm.rules. There's a tiny period of time when the _mimage device is visible during downconversion from mirror to linear. Since it is visible, we need to create the symlinks, otherwise warning messages will be issued about udev not creating those symlinks. We have to rely on udev flags completely.
2010-02-15 19:38:22 +03:00
ENV{DM_LV_NAME}=="pvmove?*|?*_vorigin", GOTO="lvm_disable"
More cleanup in udev rules: - add copyright notice for 10-dm.rules.in, - set DM_UDEV_DISABLE_{DISK, OTHER}_RULES_FLAG in 11-dm-lvm.rules directly for inappropriate and non-top-level subdevices in case we use older kernels where DM_COOKIE is not used (and therefore there are no flags passed from the LVM process itself). This applies for older kernels (version < 2.6.31), - remove unnecessary filters in 95-dm-notify.rules - the DM_COOKIE env var itself is set for change/remove udev events and for DM devices only so there's no need to double-check this.
2009-11-01 21:01:31 +03:00
ENV{DM_LV_LAYER}=="?*", GOTO="lvm_disable"
Add default udev rules. Update dm-ioctl.h comments.
2009-08-03 22:44:54 +04:00
# Create symlinks for top-level devices only.
More cleanup in udev rules: - add copyright notice for 10-dm.rules.in, - set DM_UDEV_DISABLE_{DISK, OTHER}_RULES_FLAG in 11-dm-lvm.rules directly for inappropriate and non-top-level subdevices in case we use older kernels where DM_COOKIE is not used (and therefore there are no flags passed from the LVM process itself). This applies for older kernels (version < 2.6.31), - remove unnecessary filters in 95-dm-notify.rules - the DM_COOKIE env var itself is set for change/remove udev events and for DM devices only so there's no need to double-check this.
2009-11-01 21:01:31 +03:00
ENV{DM_VG_NAME}=="?*", ENV{DM_LV_NAME}=="?*", SYMLINK+="$env{DM_VG_NAME}/$env{DM_LV_NAME}", GOTO="lvm_end"
LABEL="lvm_disable"
ENV{DM_UDEV_DISABLE_DISK_RULES_FLAG}="1"
ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}="1"
Use "nowatch" udev rule for known inappropriate devices. For now, this is just a precaution. Normally, all the other (non-dm) rules should check DM_UDEV_DISABLE_OTHER_RULES_FLAG and therefore avoid setting any inotify watches as well. But let's make sure. Support for final assignment of the "nowatch" rule (the use of ":=") will appear in next udev release, v160. This should also work in previous udev versions but the setting won't be sealed so any further OPTIONS="watch" will always prevail there. We may want to add more specific "nowatch" rules later if needed.
2010-07-07 15:22:46 +04:00
OPTIONS:="nowatch"
Add default udev rules. Update dm-ioctl.h comments.
2009-08-03 22:44:54 +04:00
LABEL="lvm_end"
Copy Permalink