summaryrefslogtreecommitdiff
path: root/man/lvmlockctl.8_main
diff options
context:
space:
mode:
Diffstat (limited to 'man/lvmlockctl.8_main')
-rw-r--r--man/lvmlockctl.8_main119
1 files changed, 119 insertions, 0 deletions
diff --git a/man/lvmlockctl.8_main b/man/lvmlockctl.8_main
new file mode 100644
index 0000000..d5b9e92
--- /dev/null
+++ b/man/lvmlockctl.8_main
@@ -0,0 +1,119 @@
+.TH "LVMLOCKCTL" "8" "LVM TOOLS #VERSION#" "Red Hat, Inc" "\""
+.
+.SH NAME
+.
+lvmlockctl \(em Control for lvmlockd
+.
+.SH SYNOPSIS
+.
+.BR lvmlockctl " [" \fIoptions ]
+.
+.SH DESCRIPTION
+.
+This command interacts with
+.BR lvmlockd (8).
+.
+.SH OPTIONS
+.
+.TP
+.BR -h | --help
+Show this help information.
+.
+.TP
+.BR -q | --quit
+Tell lvmlockd to quit.
+.
+.TP
+.BR -i | --info
+Print lock state information from lvmlockd.
+.
+.TP
+.BR -d | --dump
+Print log buffer from lvmlockd.
+.
+.TP
+.BR -w | --wait\ 0 | 1
+Wait option for other commands.
+.
+.TP
+.BR -f | --force\ 0 | 1
+Force option for other commands.
+.
+.TP
+.BR -k | --kill " " \fIvgname
+Kill access to the VG when sanlock cannot renew lease.
+.
+.TP
+.BR -r | --drop " " \fIvgname
+Clear locks for the VG when it is unused after kill (-k).
+.
+.TP
+.BR -E | --gl-enable " " \fIvgname
+Tell lvmlockd to enable the global lock in a sanlock VG.
+.
+.TP
+.BR -D | --gl-disable " " \fIvgname
+Tell lvmlockd to disable the global lock in a sanlock VG.
+.
+.TP
+.BR -S | --stop-lockspaces
+Stop all lockspaces.
+.
+.SH USAGE
+.
+.TP
+.B --info
+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.
+.
+.TP
+.B --dump
+This collects the circular log buffer of debug statements from lvmlockd
+and prints it.
+.
+.TP
+.B --kill
+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 \fBlvmlockctl --drop\fP 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
+\fBlvmlockctl --drop\fP. For more, see
+.BR lvmlockd (8).
+.
+.TP
+.B --drop
+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
+.BR lvmlockd (8).
+.
+.TP
+.B --gl-enable
+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).
+.
+.TP
+.B --gl-disable
+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).
+.
+.TP
+.B --stop-lockspaces
+This tells lvmlockd to stop all lockspaces. It can be useful to stop
+lockspaces for VGs that the \fBvgchange --lock-stop\fP 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.
+.
+.SH SEE ALSO
+.
+.BR lvm (8),
+.BR lvmlockd (8)