Hi 2010/8/18 Bryn M. Reeves <bmr@redhat.com>: > On 08/17/2010 09:16 PM, Daksh Chauhan wrote: >>> A little history and why I am asking the question in this list. >>> The customer needed to move from an existing SAN to a new SAN and wanted >>> as little as possible down time for the Application. So they zoned the >>> new SAN for access by the system and then added the new LUNs to the >>> existing Volume Group. Then ran the pvmove commands. It worked with no >>> problem on one of the PVs, but on the second one all the I/O hung at the >>> Application and any commands that access the LVM information such as >>> vgdisplay. >> >> Why not use LVM mirroring? Checkout lvconvert... > > Wrong tool for the job. There's currently no way to "split" an LVM2 > mirror leaving two usable devices (without resorting to manual edits of > the metadata anyway). > Tricky but could work : 1) Add the target PV to the VG 2) lvconvert your linear LV to mirrored (each miror leg on each PV) once synchronization is done 3) lvconvert the mirored LV to linear by removing the old PV (if lvconvert allows you to do so). > Using pvmove is the right way to approach this problem with the current > tools and since it's going to be using the same kernel infrastructure to > shovel the data around there's no guarantee the user won't run into the > same kind of problem. > > Regards, > Bryn. > > _______________________________________________ > linux-lvm mailing list > linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
