[linux-lvm] decommision disks in LVM2 & 2.6 kernel? (pvmove broken)

[Lance Dillon]

On Sun, 13 Jun 2004, Steve Wray wrote:

> Replying to my own post, I have found and installed
> the patches from;
> http://people.sistina.com/~thornber/dm/
> specifically;
> http://people.sistina.com/~thornber/dm/patches/2.6-unstable/2.6.6-rc2/2.6.6-rc2-udm1.
> tar.bz2
> 
> to a pristine 2.6.6 kernel, configured it appropriately,
> compiled and booted from it; pvmove still doesn't work.
> 
> Is there any special magick I need to apply or documentation
> that I'm missing? Do I need to update my version of pvmove
> (currently at;
> 
> pvmove --version
>   LVM version:     2.00.08 (2003-11-14)
>   Library version: 1.00.07-ioctl (2003-11-21)
>   Driver version:  4.0.0)
> (although that is as booted with the mandrake 2.6.3-13 kernel,
> not the 2.6.6 + dm patches kernel)
> 
> Thanks!
> 
> (and these disks are failing; I need to decommission them ASAP,
> if I can't pvmove the extents on them or move the files which occupy
> extents on them, then I am in trouble).
> 

I've had a problem with a pvmove failing because of errors on the disk, so 
I couldn't use pvmove at all.


First I do a lvdisplay -v on the lv's, and find which ones are on the disk 
I need to remove.  Then I create a new lv and specify a different pv to 
put it on.  Usually that meant I had to add a new disk and vgextend.  Then 
I copy all the files onto the new lv, usually using (cd /old/vol; tar cf - 
.)|(cd /new/vol; tar xvpf -).  Then I removed the old lv's, vgreduce, then 
I could remove the old disk.

It might be a long way, but it works.

l