From: matthew patton <pattonme@yahoo.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>,
"linux-lvm@lists.linux.dev" <linux-lvm@lists.linux.dev>,
Zdenek Kabelac <zdenek.kabelac@gmail.com>
Subject: Re: pvmove thin volume doesn't move
Date: Wed, 19 Nov 2025 17:22:12 +0000 (UTC) [thread overview]
Message-ID: <94679191.5310372.1763572932545@mail.yahoo.com> (raw)
In-Reply-To: <9c2a15d0-0d7d-4462-af43-83221c2ecbdd@gmail.com>
Right, so LVMThin(1) conveniently omits "Oh BTW standard functionality like pvmove() is not implemented."
lvmthin is a sub-set or sub-class of LVM, therefore any reasonable person would assume all functionality cascades down. Because it pretty much does for everything else.
> lvm2 has 'no idea' which disk space is in-use for any individual thin LV.
> (there are tools like 'thin_ls/thin_rmap' for that)
And any reasonable person would assume lvmthin would have implemented the necessary hooks so that pvmove() would work by lvmthin handing lvm back a linked-list of all of the pieces in the correct order so they could be written to lvm(thick) or to another lvmthin pool. This is not that big of a cognitive leap.
That Linux LVM thin is missing "obvious" functionality is fine, it just needs to be stated very clearly.
next prev parent reply other threads:[~2025-11-19 18:02 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
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 [this message]
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=94679191.5310372.1763572932545@mail.yahoo.com \
--to=pattonme@yahoo.com \
--cc=brian@interlinx.bc.ca \
--cc=linux-lvm@lists.linux.dev \
--cc=zdenek.kabelac@gmail.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.