[olug] LVM pvmove operation gone bad

[Jay Swackhamer]

You dont need to create a partition.
If the drive is just for LVM you should use the device without partitions.

Do the drives have identical extent sizes, like half was moved or do  
they both have 300GB of extents?

Did you do a pvmove for the drive or for the lv?

If you can, it should be ok to do shut the machine down, and bring it  
back up without the 300GB drive attached, and then try a

vgchange -a y --partial

If the LV can be activated, since the extents are on the 1TB drive,  
you can do a vgreduce --removemissing to get the sdc1 out of the VG

I'm usually working on these types of issues with an IT director and  
1000 users waiting for the system to be back up, so I may be wrong......


-- 
Jay Swackhamer
Reboot The User
402-933-6449
http://www.reboottheuser.com
http://www.cafepress.com/rtu
http://stores.ebay.com/RebootTheUser
http://www.hotr.com


Quoting Adam Lassek <adam at doubleprime.net>:

> I'm attempting to remove an old 300GB drive from my volume group and replace
> it with a shiny, new 1TB drive.
>
> The pvmove operation ran until 99.9% and then aborted. I believe this is
> because I ran pvcreate on /dev/sdf directly instead of creating a partition.
> My problem is, it moved the physical extents to /dev/sdf but the original
> drive, /dev/sdc1 is still in the volume group, and they both have identical
> extent counts. It seems that my vg has a duplicate set of extents.
>
> Every guide for removing a disk from a vg involves a pvmove and a vgreduce.
> Since the extents are duplicate, I don't want to move them; I need to remove
> them from the vg entirely. How should I do this without damaging the
> integrity of the existing volume group?
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug
>