On Fri, Dec 17, 2010 at 11:27 AM, Mauricio Tavares <raubvogel@gmail.com> wrote: > vgrename SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D export1 > WARNING: Duplicate VG name export: Existing > fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB (created here) takes precedence over > SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D > WARNING: Duplicate VG name export: Existing > fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB (created here) takes precedence over > SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D > WARNING: Duplicate VG name export: fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB > (created here) takes precedence over SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D > Volume group "export" still has active LVs > > What am I missing here? I thought if I told it to rename the vg with a given > uuid I would be golden. As you can see, that is not the case. I think you need to make the vg unavailable before you can rename it: vgchange -an SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D then your vgrename should work. Richard _______________________________________________ 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/
