diff options
| author | David Teigland <teigland@redhat.com> | 2021-03-01 15:22:54 -0600 |
|---|---|---|
| committer | David Teigland <teigland@redhat.com> | 2021-03-03 13:57:15 -0600 |
| commit | 89a3440fc0179318954855aa251b0aae4f5c1a63 (patch) | |
| tree | 66279eb0b2184402c9f08a09fbf119f7dd4c2f65 /man | |
| parent | e9d10f371199055e9ed0c2715b5353491cb759b0 (diff) | |
| download | lvm2-89a3440fc0179318954855aa251b0aae4f5c1a63.tar.gz | |
lvmlockctl: use lvm.conf lvmlockctl_kill_command
which specifies a command to run by lvmlockctl --kill.
Diffstat (limited to 'man')
| -rw-r--r-- | man/lvmlockctl.8_main | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/man/lvmlockctl.8_main b/man/lvmlockctl.8_main index b7ac0ecd6..14ce926b5 100644 --- a/man/lvmlockctl.8_main +++ b/man/lvmlockctl.8_main @@ -65,17 +65,21 @@ and prints it. .SS kill This is run by sanlock when it loses access to the storage holding leases -for a VG. It currently emits a syslog message stating that the VG must -be immediately deactivated. In the future it may automatically attempt to -forcibly deactivate the VG. For more, see +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 .BR lvmlockd (8). .SS 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. In the future, this may become automatic along with an -automatic handling of --kill. For more, see +from lvmlockd. When lvmlockctl_kill_command is used, the --kill +command may run drop automatically. For more, see .BR lvmlockd (8). .SS gl-enable |