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 09:42:30 -0500 [thread overview]
Message-ID: <20221101144230.GA11193@redhat.com> (raw)
In-Reply-To: <4b031c4d-b83a-cc92-fabf-cc9cefb4e491@bytedance.com>
On Tue, Nov 01, 2022 at 01:36:17PM +0800, Zhiyong Ye wrote:
> Hi all,
>
> I want to implement live migration of VMs in the lvm + lvmlockd + sanlock
> environment. There are multiple hosts in the cluster using the same iscsi
> connection, and the VMs are running on this environment using thinlv
> volumes. But if want to live migrate the vm, it will be difficult since
> thinlv which from the same thin pool can only be exclusive active on one
> host.
>
> I found a previous subject that discussed this issue:
>
> https://lore.kernel.org/all/20180305165926.GA20527@redhat.com/
Hi, in that email I tried to point out that the real problem is not the
locking, but rather the inability of dm-thin to share a thin pool among
multiple hosts. The locking restrictions just reflect that technical
limitation.
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 14:42 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 [this message]
2022-11-01 17:02 ` Zhiyong Ye
2022-11-01 17:57 ` David Teigland
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=20221101144230.GA11193@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.