linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@lists.linux.dev
Subject: Re: pvmove thin volume doesn't move
Date: Tue, 18 Nov 2025 18:14:01 -0500	[thread overview]
Message-ID: <81e51a5ad8f9c32610b8262447af635da81d53c3.camel@interlinx.bc.ca> (raw)
In-Reply-To: <5067ec8d-991b-4b90-ad3b-f9dbbb0472d5@gmail.com>

On Tue, 2025-11-18 at 00:37 +0100, Zdenek Kabelac wrote:
> 
> 
> Hi

Hi!

> You can always create 'new LV' on the PV you prefer to use and then
> with good 
> old 'dd'  command copy deviceA->deviceB - preferably while device
> your are 
> copying is not in use (i.e. if you are copying LV which holds your
> filesystem 
> - the partition should not be mounted) - once all your data are
> copied you 
> just reconfigure fstab to mount different new LV.

Yes, indeed, of course that is one way.  And I do appreciate the effort
of you taking the time to suggest that.  But not having to do these
kinds of off-line bulk data copy operations is one of the major
attractions of LVM.  Once we have to start reverting back to the more
cumbersome and interrupting methods the added complexity of LVM starts
to lose it's attraction and value.

> lvm2 does not (ATM) support this kind of operation.

Pity that one has to choose between efficient space use and efficient
snapshots or being able to migrate data live but cannot have both.  :-(

Is being able to do this on the roadmap at least or will this always
remain a fundamental limitation?

Cheers,
b.

  reply	other threads:[~2025-11-18 23:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16 13:27 pvmove thin volume doesn't move Brian J. Murrell
2025-11-17 15:01 ` Zdenek Kabelac
2025-11-17 23:30   ` Brian J. Murrell
2025-11-17 23:37     ` Zdenek Kabelac
2025-11-18 23:14       ` Brian J. Murrell [this message]
2025-11-19  9:16         ` Zdenek Kabelac
2025-11-19 14:07           ` Matthew Patton
2025-11-19 15:46             ` Brian J. Murrell
2025-11-19 16:34               ` Zdenek Kabelac
2025-11-19 16:06             ` Zdenek Kabelac
2025-11-19 16:36               ` Brian J. Murrell
2025-11-19 16:59                 ` Zdenek Kabelac
2025-11-19 17:22               ` matthew patton
2025-11-19 17:31                 ` Zdenek Kabelac
2025-11-19 17:38                   ` Brian J. Murrell
2025-11-19 18:11                     ` Zdenek Kabelac
2025-11-19 19:41                       ` matthew patton
2025-11-19 20:38                         ` Zdenek Kabelac
2025-11-19 16:10 ` David Teigland

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=81e51a5ad8f9c32610b8262447af635da81d53c3.camel@interlinx.bc.ca \
    --to=brian@interlinx.bc.ca \
    --cc=linux-lvm@lists.linux.dev \
    /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).