Re: Conflicting vg names but can't rename one

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Dec 17, 2010 at 2:29 PM, Mauricio Tavares <raubvogel@gmail.com> wrote:
> On 12/17/2010 01:56 PM, Richard Shaw wrote:
>>
>> 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
>>
>        Do you think I need to persuade it some more?
>
> raub@ubuntu:~$ sudo vgdisplay export
>  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
>  --- Volume group ---
>  VG Name               export
>  System ID
>  Format                lvm2
>  Metadata Areas        1
>  Metadata Sequence No  2
>  VG Access             read/write
>  VG Status             resizable
>  MAX LV                0
>  Cur LV                1
>  Open LV               1
>  Max PV                0
>  Cur PV                1
>  Act PV                1
>  VG Size               465.76 GiB
>  PE Size               4.00 MiB
>  Total PE              119234
>  Alloc PE / Size       102400 / 400.00 GiB
>  Free  PE / Size       16834 / 65.76 GiB
>  VG UUID               fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB
>
> raub@ubuntu:~$ sudo vgchange -an 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
>  Volume group "SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D" not found
> raub@ubuntu:~$
>
> Maybe I need to unmount/disconnect the hard drive with the vg being used and
> then try to rename the other drive...

When I run into things like this I go for the Live CD or Live USB
stick and boot to it. For your specific situation I would disconnect
the new drive and boot a live version of your disto (I'm not sure if
you've said what your running) or if that's not practical get a copy
of System Rescue CD[1] and boot it.

It will probably activate the volume groups by default so you'll have
to go through, "vgchange -an /dev/export" then do the "vgrename ..."

Richard

[1] http://www.sysresccd.org/Main_Page

_______________________________________________
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/



[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux