From: David Teigland <teigland@redhat.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: linux-lvm@lists.linux.dev
Subject: Re: pvmove thin volume doesn't move
Date: Wed, 19 Nov 2025 10:10:46 -0600 [thread overview]
Message-ID: <aR3sBtSk4ADdB70T@redhat.com> (raw)
In-Reply-To: <be9db13beb543be237fa069e3c72e22e1df2446c.camel@interlinx.bc.ca>
On Sun, Nov 16, 2025 at 08:27:30AM -0500, Brian J. Murrell wrote:
> Hi.
>
> I've added a new (faster) disk to a VG and now want to move a thinly
> provisioned LV to the new PV. When I try it doesn't find any data to
> move though:
>
> # pvmove -n /dev/rootvol_tmp/var /dev/sda7 /dev/sdc
> No data to move for rootvol_tmp.
Thanks for asking, one of the reasons we don't really have a plan for
this, or other things, is that we just don't get users asking for much.
Over the past couple years I've actually noticed a lot of people looking
to copy LVs, and even some external tools that have been written to do it.
There's quite a bit of variation though, and it's often copying over the
network, or recently, copying on a SAN so another host can use the LV.
There has been some work in our group aimed at parts of the problem,
for example https://github.com/device-mapper-utils/blk-archive
So, it's been at the front of mind that LV copying in some fashion is one
of the larger missing features. What's not clear to me is if we can find
a solution that meets enough of the varied use cases, but I'll try to
raise more discussion about it.
Dave
prev parent reply other threads:[~2025-11-19 16:10 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
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 [this message]
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=aR3sBtSk4ADdB70T@redhat.com \
--to=teigland@redhat.com \
--cc=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).