Your company here — click to reach over 10,000 unique daily visitors

lvmlockctl - Man Page

Control for lvmlockd


lvmlockctl [options]


This command interacts with lvmlockd(8).



Show this help information.


Tell lvmlockd to quit.


Print lock state information from lvmlockd.


Print log buffer from lvmlockd.

-w|--wait 0|1

Wait option for other commands.

-f|--force 0|1

Force option for other commands.

-k|--kill vgname

Kill access to the VG when sanlock cannot renew lease.

-r|--drop vgname

Clear locks for the VG when it is unused after kill (-k).

-E|--gl-enable vgname

Tell lvmlockd to enable the global lock in a sanlock VG.

-D|--gl-disable vgname

Tell lvmlockd to disable the global lock in a sanlock VG.


Stop all lockspaces.



This collects and displays lock state from lvmlockd.  The display is primitive, incomplete and will change in future version.  To print the raw lock state from lvmlockd, combine this option with --dump|-d.


This collects the circular log buffer of debug statements from lvmlockd and prints it.


This is run by sanlock when it loses access to the storage holding leases for a VG.  It runs the command specified in lvm.conf lvmlockctl_kill_command to deactivate LVs in the VG.  If the specified command is successful, locks will be dropped for the VG in lvmlockd (the equivalent of lvmlockctl --drop will be run.)  If no command is specified, or the command fails, then the user must intervene to forcefully deactivate LVs in the VG, and if successful, run lvmlockctl --drop.  For more, see lvmlockd(8).


This should only be run after a VG has been successfully deactivated following an lvmlockctl --kill command.  It clears the stale lockspace from lvmlockd.  When lvmlockctl_kill_command is used, the --kill command may run drop automatically.  For more, see lvmlockd(8).


This enables the global lock in a sanlock VG.  This is necessary if the VG that previously held the global lock is removed.  For more, see lvmlockd(8).


This disables the global lock in a sanlock VG.  This is necessary if the global lock has mistakenly been enabled in more than one VG.  The global lock should be disabled in all but one sanlock VG.  For more, see lvmlockd(8).


This tells lvmlockd to stop all lockspaces.  It can be useful to stop lockspaces for VGs that the vgchange --lock-stop command can no longer see, or to stop the dlm global lockspace which is not directly stopped by the vgchange command.  The wait and force options can be used with this command.

See Also

lvm(8), lvmlockd(8)

Referenced By

lvchange(8), lvconvert(8), lvcreate(8), lvdisplay(8), lvextend(8), lvm(8), lvmconfig(8), lvmdevices(8), lvmdiskscan(8), lvm-fullreport(8), lvmlockd(8), lvm-lvpoll(8), lvreduce(8), lvremove(8), lvrename(8), lvresize(8), lvs(8), lvscan(8), pvchange(8), pvck(8), pvcreate(8), pvdisplay(8), pvmove(8), pvremove(8), pvresize(8), pvs(8), pvscan(8), vgcfgbackup(8), vgcfgrestore(8), vgchange(8), vgck(8), vgconvert(8), vgcreate(8), vgdisplay(8), vgexport(8), vgextend(8), vgimport(8), vgimportclone(8), vgimportdevices(8), vgmerge(8), vgmknodes(8), vgreduce(8), vgremove(8), vgrename(8), vgs(8), vgscan(8), vgsplit(8).

LVM TOOLS 2.03.24(2) (2024-05-16) Red Hat, Inc