From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>,
"linux-lvm@lists.linux.dev" <linux-lvm@lists.linux.dev>
Subject: Re: pvmove thin volume doesn't move
Date: Wed, 19 Nov 2025 19:11:52 +0100 [thread overview]
Message-ID: <51838d90-cdd7-4e1d-bc9c-9f1ae0e29caf@gmail.com> (raw)
In-Reply-To: <cd5a3a1b5560f8634b434220a828b535c7a5ebe6.camel@interlinx.bc.ca>
Dne 19. 11. 25 v 18:38 Brian J. Murrell napsal(a):
> On Wed, 2025-11-19 at 18:31 +0100, Zdenek Kabelac wrote:
>>
>> I've been also thinking - that adding support of 'dumb' mirroring of
>> thinLV
>> into pvmove - isn't a very difficult request - so we will see -
>> although
>> obviously copying 10TiB empty thin volume isn't going to be 'a fast
>> operation' this way - but it's not any worse then a 'dd'.
>
> Not any worse than 'dd' would be more than acceptable. How can
> anything be faster at physically moving data than dd as it is usually
> only slowed by the speed of the storage in any case?
If the tool would have known 'which areas' are mapped (which knows thin-pool
target internally) then it would need to copy only those blocks.
(this can be just small fraction of the hole volume size)
On a device level - we see 'just' zero areas - but those need to be mirrored -
as on this level there no difference between 'zero' and 'unwritten' data.
(Btw with this knowledge the Joe's blk-archive tools is working)
Zdenek
next prev parent reply other threads:[~2025-11-19 18:11 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 [this message]
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=51838d90-cdd7-4e1d-bc9c-9f1ae0e29caf@gmail.com \
--to=zdenek.kabelac@gmail.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).