dmsetup
commands that support udev
integration.
Command | Description |
---|---|
dmsetup udevcomplete
|
Used to notify that udev has completed processing the rules and unlocks waiting process (called from within udev rules in 95-dm-notify.rules )
|
dmsetup udevcomplete_all
| Used for debugging purposes to manually unlock all waiting processes |
dmsetup udevcookies
| Used for debugging purposes, to show all existing cookies (system-wide semaphores) |
dmsetup udevcreatecookie
| Used to create a cookie (semaphore) manually. This is useful to run more processes under one synchronization resource. |
dmsetup udevreleasecookie
|
Used to wait for all udev processing related to all processes put under that one synchronization cookie.
|
dmsetup
options that support udev
integration are as follows.
--udevcookie
udevcreatecookie
and udevreleasecookie
:
COOKIE=$(dmsetup udevcreatecookie) dmsetupcommand
--udevcookie $COOKIE .... dmsetupcommand
--udevcookie $COOKIE .... .... dmsetupcommand
--udevcookie $COOKIE .... dmsetup udevreleasecookie --udevcookie $COOKIE
--udevcookie
option, you can just export the variable into an environment of the process:
export DM_UDEV_COOKIE=$(dmsetup udevcreatecookie) dmsetupcommand
... dmsetupcommand
... ... dmsetupcommand
...
--noudevrules
libdevmapper
itself (the old way). This option is for debugging purposes, if udev
does not work correctly.
--noudevsync
udev
synchronization. This is also for debugging purposes.
dmsetup
and its options, see the dmsetup
(8) man page.
udev
integration:
--noudevrules
: as for the dmsetup
command, disables udev
rules.
--noudevsync
: as for the dmsetup
command, disables udev
synchronization.
lvm.conf
file includes the following options that support udev
integration:
udev_rules
: enables/disables udev_rules
for all LVM2 commands globally
udev_sync
: enables/disables udev
synchronization for all LVM commands globally
lvm.conf
file options, see the inline comments in the lvm.conf
file.