From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@lists.linux.dev
Subject: pvmove thin volume doesn't move
Date: Sun, 16 Nov 2025 08:27:30 -0500 [thread overview]
Message-ID: <be9db13beb543be237fa069e3c72e22e1df2446c.camel@interlinx.bc.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
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:
# pvs
PV VG Fmt Attr PSize PFree
/dev/sda7 rootvol_tmp lvm2 a-- 170.89g 3.62g
/dev/sdc rootvol_tmp lvm2 a-- <279.46g <151.46g
# lvdisplay --maps /dev/rootvol_tmp/var
--- Logical volume ---
LV Path /dev/rootvol_tmp/var
LV Name var
VG Name rootvol_tmp
LV UUID jurBnO-APSJ-fbp1-DhWZ-8475-vrDh-heccun
LV Write Access read/write
LV Creation host, time localhost, 2019-11-10 11:11:17 -0500
LV Pool name pool00
LV Status available
# open 1
LV Size 55.27 GiB
Mapped size 96.94%
Current LE 14150
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:17
--- Segments ---
Virtual extents 0 to 14149:
Type thin
Device ID 3
The LV is a thinly provisioned LV:
# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
pool00 rootvol_tmp twi-aotz-- <138.88g 80.32 40.28
var rootvol_tmp Vwi-aotz-- 55.27g pool00 96.94
Any ideas?
Cheers,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 516 bytes --]
next reply other threads:[~2025-11-16 13:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-16 13:27 Brian J. Murrell [this message]
2025-11-17 15:01 ` pvmove thin volume doesn't move 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
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=be9db13beb543be237fa069e3c72e22e1df2446c.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 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).