From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>, linux-lvm@lists.linux.dev
Subject: Re: pvmove thin volume doesn't move
Date: Mon, 17 Nov 2025 16:01:38 +0100 [thread overview]
Message-ID: <1b6fb117-7283-4ba9-91ee-7412a2d77b3d@gmail.com> (raw)
In-Reply-To: <be9db13beb543be237fa069e3c72e22e1df2446c.camel@interlinx.bc.ca>
Dne 16. 11. 25 v 14:27 Brian J. Murrell napsal(a):
> 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.
>
> both disks are in the VG though:
Hi
lvm2 cannot move 'individual' thin volume as this volume is 'just virtual' and
uses chunks from the thin-pool.
So if you want use thinLV from a new faster storage - then whole thin-pool
must be moved to the faster storage.
And when you will be doing this - move the also _tmeta volume.
(See 'lvs -a' output for volumes you can move)
Regards
Zdenek
next prev parent reply other threads:[~2025-11-17 15:01 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 [this message]
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
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=1b6fb117-7283-4ba9-91ee-7412a2d77b3d@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 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.