From: David Teigland <teigland@redhat.com>
To: Zhiyong Ye <yezhiyong@bytedance.com>
Cc: damon.devops@gmail.com,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] How to implement live migration of VMs in thinlv after using lvmlockd
Date: Tue, 1 Nov 2022 12:57:56 -0500 [thread overview]
Message-ID: <20221101175756.GB11193@redhat.com> (raw)
In-Reply-To: <bd522c48-03df-1130-54af-bee8a58440f0@bytedance.com>
On Wed, Nov 02, 2022 at 01:02:27AM +0800, Zhiyong Ye wrote:
> Hi Dave,
>
> Thank you for your reply!
>
> Does this mean that there is no way to live migrate VMs when using lvmlockd?
You could by using linear LVs, ovirt does this using sanlock directly,
since lvmlockd arrived later.
> As you describe, the granularity of thinlv's sharing/unsharing is per
> read/write IO, except that lvmlockd reinforces this limitation for the lvm
> activation command.
>
> Is it possible to modify the code of lvmlockd to break this limitation and
> let libvirt/qemu guarantee the mutual exclusivity of each read/write IO
> across hosts when live migration?
lvmlockd locking does not apply to the dm i/o layers. The kind of
multi-host locking that you seem to be talking about would need to be
implemented inside dm-thin to protect on-disk data structures that it
modifies. In reality you would need to write a new dm target with locking
and data structures designed for that kind of sharing.
Dave
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2022-11-01 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 5:36 [linux-lvm] How to implement live migration of VMs in thinlv after using lvmlockd Zhiyong Ye
2022-11-01 14:42 ` David Teigland
2022-11-01 17:02 ` Zhiyong Ye
2022-11-01 17:57 ` David Teigland [this message]
2022-11-01 18:15 ` Demi Marie Obenour
2022-11-02 9:18 ` Zhiyong Ye
2022-11-02 9:01 ` Zhiyong Ye
2022-11-01 18:08 ` Stuart D Gathman
2022-11-02 9:31 ` Zhiyong Ye
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221101175756.GB11193@redhat.com \
--to=teigland@redhat.com \
--cc=damon.devops@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=yezhiyong@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).