From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@lists.linux.dev
Subject: Re: pvmove thin volume doesn't move
Date: Wed, 19 Nov 2025 10:46:25 -0500 [thread overview]
Message-ID: <f53f9eb8b6bcd3cc0da29817f9e683ea32c69e44.camel@interlinx.bc.ca> (raw)
In-Reply-To: <6D706D06-AB0F-4C55-9F68-E8E07926A511@yahoo.com>
On Wed, 2025-11-19 at 09:07 -0500, Matthew Patton wrote:
>
> That is one hell of a wild and unsupported assumption.
Yeah, I too was going to challenge that statement that I was a "lonely"
outlier in the community of LVM users that would want to be able to
move a thinly-provisioned LV from one PV to another, just as non-
thinly-provisioned LVs can be.
> Practically nobody , even seasoned sysadmins would know of this
> deficiency.
Indeed, I was skeptical that this was commonly understood as well.
Well by anyone who had not tried it as I did only to find it is not
supported.
It does suck to have to choose between feature sets that are both very
useful.
Cheers,
b.
next prev parent reply other threads:[~2025-11-19 15:46 UTC|newest]
Thread overview: 20+ 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 [this message]
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
2025-11-24 8:25 ` David Greaves
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=f53f9eb8b6bcd3cc0da29817f9e683ea32c69e44.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 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.