2015-09-04 19:02:48 +03:00
.TH "LVMLOCKCTL" "8" "LVM TOOLS #VERSION#" "Red Hat, Inc" "\""
.SH NAME
lvmlockctl \(em Control for lvmlockd
.SH DESCRIPTION
This command interacts with
.BR lvmlockd (8).
.SH OPTIONS
lvmlockctl [options]
2017-03-27 17:45:48 +03:00
.B --help | -h
2015-09-04 19:02:48 +03:00
Show this help information.
2017-03-27 17:45:48 +03:00
.B --quit | -q
2015-09-04 19:02:48 +03:00
Tell lvmlockd to quit.
2017-03-27 17:45:48 +03:00
.B --info | -i
2015-09-04 19:02:48 +03:00
Print lock state information from lvmlockd.
2017-03-27 17:45:48 +03:00
.B --dump | -d
2015-09-04 19:02:48 +03:00
Print log buffer from lvmlockd.
2017-03-27 17:45:48 +03:00
.B --wait | -w 0|1
2015-09-04 19:02:48 +03:00
Wait option for other commands.
2017-03-27 17:45:48 +03:00
.B --force | -f 0|1
2015-09-04 19:02:48 +03:00
Force option for other commands.
2017-03-27 17:45:48 +03:00
.B --kill | -k
2015-09-04 19:02:48 +03:00
.I vgname
Kill access to the VG when sanlock cannot renew lease.
2017-03-27 17:45:48 +03:00
.B --drop | -r
2015-09-04 19:02:48 +03:00
.I vgname
Clear locks for the VG when it is unused after kill (-k).
2017-03-27 17:45:48 +03:00
.B --gl-enable | -E
2015-09-04 19:02:48 +03:00
.I vgname
Tell lvmlockd to enable the global lock in a sanlock VG.
2017-03-27 17:45:48 +03:00
.B --gl-disable | -D
2015-09-04 19:02:48 +03:00
.I vgname
Tell lvmlockd to disable the global lock in a sanlock VG.
2017-03-27 17:45:48 +03:00
.B --stop-lockspaces | -S
2015-09-04 19:02:48 +03:00
Stop all lockspaces.
.SH USAGE
.SS info
This collects and displays lock state from lvmlockd. The display is
primitive, incomplete and will change in future version. To print the raw
2017-03-27 17:45:48 +03:00
lock state from lvmlockd, combine this option with --dump|-d.
2015-09-04 19:02:48 +03:00
.SS dump
This collects the circular log buffer of debug statements from lvmlockd
and prints it.
.SS kill
This is run by sanlock when it loses access to the storage holding leases
2021-03-02 00:22:54 +03:00
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
2015-09-04 19:02:48 +03:00
.BR lvmlockd (8).
.SS drop
This should only be run after a VG has been successfully deactivated
2017-03-27 17:45:48 +03:00
following an lvmlockctl --kill command. It clears the stale lockspace
2021-03-02 00:22:54 +03:00
from lvmlockd. When lvmlockctl_kill_command is used, the --kill
command may run drop automatically. For more, see
2015-09-04 19:02:48 +03:00
.BR lvmlockd (8).
2017-03-27 17:45:48 +03:00
.SS gl-enable
2015-09-04 19:02:48 +03:00
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
.BR lvmlockd (8).
2017-03-27 17:45:48 +03:00
.SS gl-disable
2015-09-04 19:02:48 +03:00
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
.BR lvmlockd (8).
2017-03-27 17:45:48 +03:00
.SS stop-lockspaces
2015-09-04 19:02:48 +03:00
This tells lvmlockd to stop all lockspaces. It can be useful to stop
2017-03-27 17:45:48 +03:00
lockspaces for VGs that the vgchange --lock-stop comand can no longer
2015-09-04 19:02:48 +03:00
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.