summaryrefslogtreecommitdiff
path: root/udev/11-dm-lvm.rules.in
Commit message (Collapse)AuthorAgeFilesLines
* udev: remove unsupported OPTIONS+="event_timeout" rulePeter Rajnoha2019-08-131-2/+0
| | | | | | | | | | | | The OPTIONS+="event_timeout" is Unsupported since systemd/udev version 216, that is ~5 years ago. Since systemd/udev version 243, there's a new message printed if unsupported OPTIONS value is used: Invalid value for OPTIONS key, ignoring: 'event_timeout=180' Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1740666
* udev: clear temporary variable properlyPeter Rajnoha2014-01-201-1/+1
| | | | | | Clear temporary DM_DISABLE_OTHER_RULES_FLAG properly. This did not cause any bug or problem as the temporary variable is overwritten next time it's used again, but we should still clean it properly!
* udev: proper reset of DM_UDEV_DISABLE_OTHER_RULES_FLAG and honour this flag ↵Peter Rajnoha2013-10-291-1/+1
| | | | | | | | | | | | | | | | | | in lvmetad rules Reset the DM_UDEV_OTHER_RULES_FLAG to original value right at the time of dropping the DM_NOSCAN flag. When DM_NOSCAN is set, the DM_UDEV_DISABLE_OTHER_RULES_FLAG is also set to avoid udev processing in "other/foreign" rules. If the noscan flag is dropped, the DM_UDEV_DISABLE_OTHER_RULES_FLAG should be reset to its original value. Also, lvmetad should respect the DM_UDEV_DISABLE_OTHER_RULES_FLAG because if the volume is set with this flag it: - definitely is not a top-level device (so makes no sense for lvmetad scanning) - is not supposed to be scanned further (for any stacking on top of it, including LVM stacking itself and any autoactivation of stacked LVs)
* udev: add support for "NOSCAN" flagPeter Rajnoha2013-10-081-0/+15
| | | | | | | | | | | 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...
* udev: fix 3min udev timeout so that it is applied for all LVM volumesPeter Rajnoha2013-09-271-2/+2
| | | | The timeout should be set before any volume skipping.
* udev: override new udev default timeout of 30s to original 3minPeter Rajnoha2013-09-111-0/+2
| | | | | | | | | | New versions of udev changed the default event timeout to 30s from original 3min. This causes problems with LVM processes that starve because of the IO load caused by some LVM actions (e.g. mirror/raid synchronization). Reinstate the 3min udev timeout for now until we optimize this in a way that even the 30s timeout is sufficient.
* udev: udev rules cleanupPeter Rajnoha2012-06-271-0/+37
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!