Linux LVM users
 help / color / mirror / Atom feed
From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Zhiyong Ye <yezhiyong@bytedance.com>
Cc: damon.devops@gmail.com
Subject: Re: [linux-lvm] How to implement live migration of VMs in thinlv after using lvmlockd
Date: Tue, 1 Nov 2022 14:15:23 -0400	[thread overview]
Message-ID: <Y2FiO90/LQ/Pi3SN@itl-email> (raw)
In-Reply-To: <20221101175756.GB11193@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 547 bytes --]

On Tue, Nov 01, 2022 at 12:57:56PM -0500, David Teigland wrote:
> 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.

Another approach would be to use thin provisioning on the SAN instead of
at the LVM level.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

_______________________________________________
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/

  reply	other threads:[~2022-11-01 18:16 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
2022-11-01 18:15       ` Demi Marie Obenour [this message]
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=Y2FiO90/LQ/Pi3SN@itl-email \
    --to=demi@invisiblethingslab.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