All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: linux-lvm@lists.linux.dev
Subject: Re: pvmove thin volume doesn't move
Date: Tue, 18 Nov 2025 00:37:12 +0100	[thread overview]
Message-ID: <5067ec8d-991b-4b90-ad3b-f9dbbb0472d5@gmail.com> (raw)
In-Reply-To: <29209080-c09b-40df-86c3-f22c1d7f6520@interlinx.bc.ca>

Dne 18. 11. 25 v 0:30 Brian J. Murrell napsal(a):
> Pity.  I don't really want to move all of the LVs in the pool.
> 
> Can I create a new pool on the new PV and move just the one LV from one pre-existing pool to the new pool?
> 
> Cheers,
> b.
> 
> 

Hi

You can always create 'new LV' on the PV you prefer to use and then with good 
old 'dd'  command copy deviceA->deviceB - preferably while device your are 
copying is not in use (i.e. if you are copying LV which holds your filesystem 
- the partition should not be mounted) - once all your data are copied you 
just reconfigure fstab to mount different new LV.

lvm2 does not (ATM) support this kind of operation.

Regards

Zdenek

  reply	other threads:[~2025-11-17 23:37 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 [this message]
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=5067ec8d-991b-4b90-ad3b-f9dbbb0472d5@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.