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
24943fe9d3
lvm2/udev/13-dm-disk.rules.in

58 lines
2.2 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 device-mapper devices.
#
# These rules create symlinks in /dev/disk directory.
# Symlinks that depend on probing filesystem type,
# label and uuid are created only if the device is not
# suspended.
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="dm_end"
Remove 'last_rule' from udev rules. 'last_rule' option has been removed from udev (version >= 147). From now on, we require foreign rules to check and honor ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG} instead. Foreign rules should be skipped totally when this flag is set.
2009-11-13 15:33:27 +03:00
ENV{DM_UDEV_RULES_VSN}!="?*", GOTO="dm_end"
ENV{DM_UDEV_DISABLE_DISK_RULES_FLAG}=="1", GOTO="dm_end"
Add default udev rules. Update dm-ioctl.h comments.
2009-08-03 22:44:54 +04:00
SYMLINK+="disk/by-id/dm-name-$env{DM_NAME}"
ENV{DM_UUID}=="?*", SYMLINK+="disk/by-id/dm-uuid-$env{DM_UUID}"
dm udev rules: don't export and save DM_SUSPENDED DM_SUSPENDED is a device-mapper internal flag, which is not intended to be used by other rules, and which is determined by 10-dm.rules from sysfs for every uevent. Rename it to ".DM_SUSPENDED", so that it won't be saved in the udev database. Known consumers of DM_SUSPENDED are 66-kpartx.rules (from multipath-tools) and 99-systemd.rules (from systemd). These will have to be adapted. 11-dm-mpath.rules will be changed to use .DM_SUSPENDED. Signed-off-by: Martin Wilck <mwilck@suse.com> Reviewed-by: Peter Rajnoha <prajnoha@redhat.com>
2024-03-01 17:16:33 +03:00
ENV{.DM_SUSPENDED}=="1", ENV{DM_UDEV_PRIMARY_SOURCE_FLAG}=="1", GOTO="dm_import"
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_NOSCAN}=="1", ENV{DM_UDEV_PRIMARY_SOURCE_FLAG}=="1", GOTO="dm_import"
dm udev rules: don't export and save DM_SUSPENDED DM_SUSPENDED is a device-mapper internal flag, which is not intended to be used by other rules, and which is determined by 10-dm.rules from sysfs for every uevent. Rename it to ".DM_SUSPENDED", so that it won't be saved in the udev database. Known consumers of DM_SUSPENDED are 66-kpartx.rules (from multipath-tools) and 99-systemd.rules (from systemd). These will have to be adapted. 11-dm-mpath.rules will be changed to use .DM_SUSPENDED. Signed-off-by: Martin Wilck <mwilck@suse.com> Reviewed-by: Peter Rajnoha <prajnoha@redhat.com>
2024-03-01 17:16:33 +03:00
ENV{.DM_SUSPENDED}=="1", GOTO="dm_end"
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_NOSCAN}=="1", GOTO="dm_watch"
Add default udev rules. Update dm-ioctl.h comments.
2009-08-03 22:44:54 +04:00
Call built-in blkid conditionaly (udev version >= 176), call standard blkid with full path otherwise.
2012-02-20 23:38:40 +04:00
(BLKID_RULE)
udev: import previous results of blkid when in suspended state Follow-up for e10f67e91728f1e576803df884049ecbd92874d0. The commit e10f67e91728f1e576803df884049ecbd92874d0 tries to keep device node symlinks even if the device is in the suspended state. However, necessary properties that may previously obtained by the blkid command were not imported at least in the .rules file. So, unless ID_FS_xyz properties are imported by another earlier .rules file, the device node symlinks are still lost when event is processed in the suspended state. Let's explicitly import the necessary properties. RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=2158628 GHPR: https://github.com/lvmteam/lvm2/pull/105
2023-02-01 18:28:12 +03:00
GOTO="dm_link"
LABEL="dm_import"
13-dm-disk.rules: import ID_FS_TYPE ID_FS_TYPE is the most important udev property for most follow-up rules. It must be imported from the udev db if blkid can't be run. Signed-off-by: Martin Wilck <mwilck@suse.com> Reviewed-by: Peter Rajnoha <prajnoha@redhat.com>
2024-03-01 21:41:41 +03:00
IMPORT{db}="ID_FS_TYPE"
udev: import previous results of blkid when in suspended state Follow-up for e10f67e91728f1e576803df884049ecbd92874d0. The commit e10f67e91728f1e576803df884049ecbd92874d0 tries to keep device node symlinks even if the device is in the suspended state. However, necessary properties that may previously obtained by the blkid command were not imported at least in the .rules file. So, unless ID_FS_xyz properties are imported by another earlier .rules file, the device node symlinks are still lost when event is processed in the suspended state. Let's explicitly import the necessary properties. RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=2158628 GHPR: https://github.com/lvmteam/lvm2/pull/105
2023-02-01 18:28:12 +03:00
IMPORT{db}="ID_FS_USAGE"
IMPORT{db}="ID_FS_UUID_ENC"
IMPORT{db}="ID_FS_LABEL_ENC"
IMPORT{db}="ID_PART_ENTRY_NAME"
IMPORT{db}="ID_PART_ENTRY_UUID"
IMPORT{db}="ID_PART_ENTRY_SCHEME"
IMPORT{db}="ID_PART_GPT_AUTO_ROOT"
udev: create symlinks and watch even in suspended state If a dm device is suspended, we can't run blkid on it. But earlier rules (e.g. 11-dm-parts.rules) might have imported previously scanned properties from the udev db, in particular if the device had been correctly set up beforehand (DM_UDEV_PRIMARY_SOURCE_FLAG==1). Symlinks for existing ID_FS_xyz properties must be preserved in this case. Otherwise lower-priority devices (such as multipath components) might take over the symlink temporarily. Likewise, we should't stop watching a temporarily suspended, but previously correctly configured dm device. Signed-off-by: Martin Wilck <mwilck@suse.com>
2022-01-28 16:42:29 +03:00
LABEL="dm_link"
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
ENV{DM_UDEV_LOW_PRIORITY_FLAG}=="1", OPTIONS="link_priority=-100"
Add default udev rules. Update dm-ioctl.h comments.
2009-08-03 22:44:54 +04:00
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
udev: create /dev/disk/by-label symlinks for DM devs that have crypto as next layer We already create /dev/disk/by-uuid symlinks for DM devices which contain crypto-type as next layer (as identified by blkid). Also create /dev/disk/by-label symlinks as the labels can be defined for crypto-type devices too. Reported and fix suggested by: Patrick Plenefisch <simonpatp@gmail.com> See also: https://lore.kernel.org/lvm-devel/CAOCpoWfYjOVNJNt+cnOVXDHiDq2wRogTqBijcUoa7chqOLRa5Q@mail.gmail.com/
2024-03-25 12:16:04 +03:00
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_LABEL_ENC}=="?*", SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}"
udev: also create /dev/disk/by-part{label,uuid} and gpt-auto-root symlinks The blkid we call in 13-dm-disk.rules also returns identifiers for partitions based on which the /dev/disk/by-part{uuid,label} and gpt-auto-root symlinks should be created in the same manner as we already create symlinks for filesystem labels and uuids. This is because we handle blkid calls and symlink creation under /dev/disk ourselves in our 13-dm-disk.rules for device-mapper devices for us to have more control over this process. See also https://lists.freedesktop.org/archives/systemd-devel/2017-July/039220.html and original report http://tracker.ceph.com/issues/19489 for the exact case where these symlinks were missing.
2017-07-10 13:35:53 +03:00
ENV{ID_PART_ENTRY_UUID}=="?*", SYMLINK+="disk/by-partuuid/$env{ID_PART_ENTRY_UUID}"
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_ENTRY_NAME}=="?*", SYMLINK+="disk/by-partlabel/$env{ID_PART_ENTRY_NAME}"
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_GPT_AUTO_ROOT}=="1", SYMLINK+="gpt-auto-root"
Add default udev rules. Update dm-ioctl.h comments.
2009-08-03 22:44:54 +04:00
Add watch rule to 13-dm-disk.rules. We don't have anything better yet... The problems the watch rule caused when removing devices should be covered now with the "retry remove" logic. It's also better to have this maintained by us, rather than having this rule anywhere else without proper control.
2012-02-15 18:50:33 +04:00
# Add inotify watch to track changes on this device.
typo
2012-02-15 19:10:31 +04:00
# Using the watch rule is not optimal - it generates a lot of spurious
Add watch rule to 13-dm-disk.rules. We don't have anything better yet... The problems the watch rule caused when removing devices should be covered now with the "retry remove" logic. It's also better to have this maintained by us, rather than having this rule anywhere else without proper control.
2012-02-15 18:50:33 +04:00
# and useless events whenever the device opened for read-write is closed.
# The best would be to generete the event directly in the tool changing
# relevant information so only relevant events will be processed
# (like creating a filesystem, changing filesystem label etc.).
#
# But let's use this until we have something better...
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
LABEL="dm_watch"
Add watch rule to 13-dm-disk.rules. We don't have anything better yet... The problems the watch rule caused when removing devices should be covered now with the "retry remove" logic. It's also better to have this maintained by us, rather than having this rule anywhere else without proper control.
2012-02-15 18:50:33 +04:00
OPTIONS+="watch"
Add default udev rules. Update dm-ioctl.h comments.
2009-08-03 22:44:54 +04:00
LABEL="dm_end"
Copy Permalink