LVM2 problems

[Herta Van den Eynde]

On 08/04/2008, Ezra Taylor <ezra.taylor at gmail.com> wrote:
>
> Hello all:
>               I just inherited a box that's running LVM2.  This box has
> two
> volume groups with the same name but they both have different UUID
> numbers.
> Is it a problem to have a  box like this?  If so, how can I recover?  The
> output of displayvg and pvscan is below.
>
>
>   sudo /usr/sbin/vgdisplay
>   --- Volume group ---
>   VG Name               SysVG
>   System ID
>   Format                lvm2
>   Metadata Areas        1
>   Metadata Sequence No  8
>   VG Access             read/write
>   VG Status             resizable
>   MAX LV                0
>   Cur LV                7
>   Open LV               7
>   Max PV                0
>   Cur PV                1
>   Act PV                1
>   VG Size               273.38 GB
>   PE Size               32.00 MB
>   Total PE              8748
>   Alloc PE / Size       2112 / 66.00 GB
>   Free  PE / Size       6636 / 207.38 GB
>   VG UUID               rS82Le-cEA5-MDxm-7zza-x0ve-gxYp-txZQT0
>
>   --- Volume group ---
>   VG Name               SysVG
>   System ID
>   Format                lvm2
>   Metadata Areas        1
>   Metadata Sequence No  8
>   VG Access             read/write
>   VG Status             resizable
>   MAX LV                0
>   Cur LV                7
>   Open LV               7
>   Max PV                0
>   Cur PV                1
>   Act PV                1
>   VG Size               67.94 GB
>   PE Size               32.00 MB
>   Total PE              2174
>   Alloc PE / Size       2112 / 66.00 GB
>   Free  PE / Size       62 / 1.94 GB
>   VG UUID               haTLf2-kby5-fPxh-pVGx-7lD5-ZYpa-nI6EvK
>
>
>
>   sudo /usr/sbin/pvscan
>   PV /dev/cciss/c0d1p1   VG SysVG   lvm2 [273.38 GB / 207.38 GB free]
>   PV /dev/cciss/c0d0p2   VG SysVG   lvm2 [67.94 GB / 1.94 GB free]
>   Total: 2 [341.31 GB] / in use: 2 [341.31 GB] / in no VG: 0 [0   ]
>
>
> --
> Ezra Taylor
>

I suppose that this could be caused when exporting/importing volume groups
from another system.
You could try to rename one of the volume groups using vgsplit.  It has a -t
option to test first, so you should be save.  Something like this should do
the trick:

   # vgsplit -A y -t SysVG MyVG /dev/cciss/c0d0p2

If this looks OK, repeat without the "-t" option.

Kind regards,

Herta

-- 
"Life on Earth may be expensive,
but it comes with a free ride around the Sun."