LVM1 actually handled this very well. With LVM1 it would rename the VG, appending "PV_EXP" to the VG name when exporting it. This essentially would allow creating a new VG with the same original name. I am kind of surprised this did not carry over to LVM2. I understand that the easiest solution would be to not be in this situation. Unfortunately, my company develops disaster recovery software that allows users to create/re-create/migrate LVM disk configuration. We need to be very careful about how we detect and create PV's/VG's. On Fri, 2003-10-10 at 12:01, Alasdair G Kergon wrote: > > i have run into a situation where lvm2 does not behave the same as lvm1. > > basically i want to be able to create a vg with the same name as an > > exported vg. > > > is this a bug within lvm2, is it no longer possible with lvm2, or is > > there a different procedure to accomplish this? > > The LVM2 tools get confused if they see 2 VGs (1 live, 1 exported) with > the same name. It is not trivial to change to tools to cope with this, > so for now, you should avoid getting into this situation. [If > necessary, use lvm.conf filters to hide the exported PVs while you > rename the live VG to something else.] > > Alasdair _______________________________________________ linux-lvm mailing list linux-lvm@sistina.com http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
