with the pvcreate/vgextend/pvmove/vgreduce
> > > steps.
> >
> > I crossed my fingers and tried it, and it worked. Rather than removing
> > LVM I've decided to just live with it. The alternative is a system
> > reinstall.
>
> You were in the lucky po
it, and it worked. Rather than removing
LVM I've decided to just live with it. The alternative is a system
reinstall.
You were in the lucky position of having LVM, which makes this kind of
"move to new disk" operations trivial. Doing a disk clone was
exactly the wrong way to do it, you've inadvertently
On Mon, 2019-12-02 at 12:44 -0600, Roger Heflin wrote:
> it might be if you use dd to clear only the duplicate pv/lvm partition
> header and then start with the pvcreate/vgextend/pvmove/vgreduce
> steps.
I crossed my fingers and tried it, and it worked. Rather than removing
LVM I'v
On 12/2/19 9:59 AM, Patrick O'Callaghan wrote:
On Mon, 2019-12-02 at 11:19 -0600, Roger Heflin wrote:
Doing just about anything is going to be really dangerous and tricky
given the device has duplicate uuids at the LV and PV level. There
are ways to fix it, but most of those ways will either
it might be if you use dd to clear only the duplicate pv/lvm partition
header and then start with the pvcreate/vgextend/pvmove/vgreduce
steps.
On Mon, Dec 2, 2019 at 12:39 PM Patrick O'Callaghan
wrote:
>
> On Mon, 2019-12-02 at 12:16 -0600, Roger Heflin wrote:
> > The easiest way to move an vg
On Mon, 2019-12-02 at 12:16 -0600, Roger Heflin wrote:
> The easiest way to move an vg to a new device is partitioning the new
> device, create a pv on the correct device, and then add that device to
> the vg and then do a pvmove to move the data to the new device. Once
> done you remove the
On Mon, 2019-12-02 at 18:12 +, Alasdair G Kergon wrote:
> On Mon, Dec 02, 2019 at 12:46:57PM +, Patrick O'Callaghan wrote:
> > Anyway, I cloned each partition using dd, but of course that also
> > cloned the LVM stuff, including the LVM identifiers
> > How can I blow away LVM on the cloned
The easiest way to move an vg to a new device is partitioning the new
device, create a pv on the correct device, and then add that device to
the vg and then do a pvmove to move the data to the new device. Once
done you remove the device from the vg.
cloning the boot can be done with dd, but if
On Mon, Dec 02, 2019 at 12:46:57PM +, Patrick O'Callaghan wrote:
> Anyway, I cloned each partition using dd, but of course that also
> cloned the LVM stuff, including the LVM identifiers
> How can I blow away LVM on the cloned drive without having to start
> again from scratch?
Maybe
On Mon, 2019-12-02 at 11:19 -0600, Roger Heflin wrote:
>
> Doing just about anything is going to be really dangerous and tricky
> given the device has duplicate uuids at the LV and PV level. There
> are ways to fix it, but most of those ways will either be exactly
> right, exactly wrong and you
do "dmsetup table" and see if there is a mapping to the device you
want to get rid of.
If there is no mapping you may be able to exclude the device with a
filter in /etc/lvm/lvm.conf or you may have to used the really
dangerous commands to clear the data of the disk.
Doing just about anything is
On Mon, 2019-12-02 at 21:05 +0800, Ed Greshko wrote:
> > How can I blow away LVM on the cloned drive without having to start
> > again from scratch?
> >
>
> Are you looking for commands like lvremove and pvremove?
I'd already looked at those.
lvremove takes an LV identifier as argument, but
On Mon, Dec 2, 2019, 20:47 Patrick O'Callaghan
wrote:
> I'm in the process of trying to clone an existing drive to a new SSD.
> The existing drive was created by a fresh F31 install, which used LVM
> for root and swap. I normally turn this off when installing but didn't
> this time, either
I'm in the process of trying to clone an existing drive to a new SSD.
The existing drive was created by a fresh F31 install, which used LVM
for root and swap. I normally turn this off when installing but didn't
this time, either because it's not possible or because I couldn't find
the magic
14 matches
Mail list logo
