Re: pvmove broken? netbsd-6 (xen dom 0)

[Louis Guillaume <louis%zabrico.com@localhost>]

On 5/27/13 3:32 AM, haad wrote:
> Hi,
>
> You need a pvmove target for that and that one is not yet available in
> NetBSD. @ahoka wrote it in last year gsoc for DragonFlyBSD and I need
> to find time to import it in to the NetBSD.


Ok - Can you suggest a workaround for moving extents to a different PV? 
At this point the plan is to create a separate VG, put the new PV there, 
create an LV for it and then mount, dump/restore. If there's a simpler 
way, please let me know. Thanks,

Louis

> On Mon, May 27, 2013 at 8:37 AM, Louis Guillaume <louis%zabrico.com@localhost> 
> wrote:
> > Hi,
> >
> > I'm trying to get rid of a physical volume, replacing it with another. This
> > appears to be a job for "pvmove". I added the new PV to the volume group and
> > then attempted a "pvmove" to transfer the extents to the other disk. But it
> > fails as shown below. Any help would be great:
> >
> > Louis
> >
> > # pvmove /dev/rraid0e
> >    Required device-mapper target(s) not detected in your kernel
> > # pvdisplay
> >    --- Physical volume ---
> >    PV Name               /dev/rraid0e
> >    VG Name               vg0
> >    PV Size               1.81 TiB / not usable 4.00 MiB
> >    Allocatable           yes
> >    PE Size               4.00 MiB
> >    Total PE              475779
> >    Free PE               441987
> >    Allocated PE          33792
> >    PV UUID               oJNnXc-qGId-VBKS-QkQ9-8VJ9-Ya3n-267gAC
> >
> >    --- Physical volume ---
> >    PV Name               /dev/rraid1e
> >    VG Name               vg0
> >    PV Size               1.81 TiB / not usable 4.00 MiB
> >    Allocatable           yes
> >    PE Size               4.00 MiB
> >    Total PE              475779
> >    Free PE               475779
> >    Allocated PE          0
> >    PV UUID               0POJIH-ffRs-dGA3-eZU6-PGAa-PGak-dspdNx