shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2025-01-18 10:04:20 +03:00
Code Releases Activity

man lvmlockd: explain the use of lvmlockctl kill

Browse Source
This commit is contained in:
David Teigland 2015-09-04 10:29:01 -05:00
parent 55c13f3de4
commit b00ee99a21
1 changed files with 20 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
man/lvmlockd.8.in
View File

@ -536,7 +536,7 @@ Run vgchange \-\-lock-stop <vgname> on all other hosts before vgremove.
have stopped.) have stopped.)
A sanlock VG contains a hidden LV called "lvmlock" that holds the sanlock A sanlock VG contains a hidden LV called "lvmlock" that holds the sanlock
locks. vgreduce cannot yet remove the PV holding the lvmlockd LV. To locks. vgreduce cannot yet remove the PV holding the lvmlock LV. To
remove this PV, change the VG lock type to "none", run vgreduce, then remove this PV, change the VG lock type to "none", run vgreduce, then
change the VG lock type back to "sanlock". change the VG lock type back to "sanlock".
@ -590,13 +590,20 @@ the dlm/corosync recovery process is complete.
.B sanlock lease storage failure .B sanlock lease storage failure
If a host loses access to the device holding a VG's locks, sanlock cannot If the PV under a sanlock VG's lvmlock LV is disconnected, unresponsive or
renew its lease for the VG's locks. After some time, the lease will too slow, sanlock cannot renew the lease for the VG's locks. After some
expire, and locks held by the host can be acquired by other hosts. time, the lease will expire, and locks that the host owns in the VG can be
acquired by other hosts. The VG must be forcibly deactivated on the host
with the expiring lease before other hosts can acquire its locks.
If no LVs are active in the VG, the lockspace with an expiring lease will When the sanlock daemon detects that the lease storage is lost, it runs
be shut down, and errors will be reported when trying to use the VG. Use the command lvmlockctl \-\-kill <vgname>. This command emits a syslog
the lvmlockctl \-\-drop command to clear the stale lockspace from message stating that lease storage is lost for the VG and LVs must be
immediately deactivated.
If no LVs are active in the VG, then the lockspace with an expiring lease
will be removed, and errors will be reported when trying to use the VG.
Use the lvmlockctl \-\-drop command to clear the stale lockspace from
lvmlockd. lvmlockd.
If the VG has active LVs when the lock storage is lost, the LVs must be If the VG has active LVs when the lock storage is lost, the LVs must be
@ -607,9 +614,12 @@ about 40 seconds, sanlock will reset the host using the local watchdog.
The machine reset is effectively a severe form of "deactivating" LVs The machine reset is effectively a severe form of "deactivating" LVs
before they can be activated on other hosts. The reset is considered a before they can be activated on other hosts. The reset is considered a
better alternative than having LVs used by multiple hosts at once, which better alternative than having LVs used by multiple hosts at once, which
could easily damage or destroy their content. A future enhancement may could easily damage or destroy their content.
automatically attempt to forcibly deactivate LVs before the lockspace
lease expires. In the future, the lvmlockctl kill command may automatically attempt to
forcibly deactivate LVs before the sanlock lease expires. Until then, the
user must notice the syslog message and manually deactivate the VG before
sanlock resets the machine.
.B sanlock daemon failure .B sanlock daemon failure