archive mirror
 help / color / mirror / Atom feed
From: Damon Wang <>
Subject: [linux-lvm] [lvmlockd] Refresh lvmlockd leases after sanlock changes
Date: Mon, 5 Mar 2018 16:37:58 +0800	[thread overview]
Message-ID: <> (raw)

[-- 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 --]

             reply	other threads:[~2018-03-05  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05  8:37 Damon Wang [this message]
2018-03-05 16:59 ` [linux-lvm] [lvmlockd] Refresh lvmlockd leases after sanlock changes David Teigland
2018-03-07  5:50   ` Damon Wang
2018-03-07  7:11     ` Damon Wang
2018-03-07  8:14   ` Damon Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).