archive mirror
 help / color / mirror / Atom feed
* [linux-lvm] [lvmlockd] Refresh lvmlockd leases after sanlock changes
@ 2018-03-05  8:37 Damon Wang
  2018-03-05 16:59 ` David Teigland
  0 siblings, 1 reply; 5+ messages in thread
From: Damon Wang @ 2018-03-05  8:37 UTC (permalink / raw)
  To: linux-lvm

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

Hi all,

I made a environment lvm + lvmlockd + sanlock.

After active a lv with exclusive, we can see lock status via "lvmlockctl
-i" or "sanlock status" and it must be agreed.

But if use "sanlock client release -r xxxxxxx" to release the lock
manually, "lvmlockctl -i" shows as previous which means lvmlockd still
thinks the lock held, meanwhile other hosts now can get the lock.

So is there any way to refresh lock lease inside lvmlockd?




Why I have such question and environment?

I want to run vms on some hosts with a SAN, my plan is all hosts will login
to SAN and provide a lun as lvm pv. Each vm gets a thin lv from lvm as root
volume, and maybe some other thin lvs as data volume. So lvmlockd will
assurance only one host will change metadata at same time, and lvmthin will
provide thin provision.

But if want to live migrate the vm, it could be difficult since thin lv can
only be exclusive active on one host, if you want to active on another
host, the only way I find is use sanlock to release it manually. If you
have a better way, please tell me and thanks a loooot !!!

[-- Attachment #2: Type: text/html, Size: 2236 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2018-03-07  8:14 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-05  8:37 [linux-lvm] [lvmlockd] Refresh lvmlockd leases after sanlock changes Damon Wang
2018-03-05 16:59 ` David Teigland
2018-03-07  5:50   ` Damon Wang
2018-03-07  7:11     ` Damon Wang
2018-03-07  8:14   ` Damon Wang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).