LVM and VxVM

Volume Group belongs to different CPU ID

 
SOLVED
Go to solution
skt_skt
Honored Contributor

Volume Group belongs to different CPU ID

vgimport: Warning: Volume Group belongs to different CPU ID.
Can not determine if Volume Group is in use on another system. Continuing.
vgimport: Warning: Volume Group contains "9" PVs, "26" specified. Continuing.

Could some one explain why the Warning about different CPU ID
4 REPLIES 4
A. Clay Stephenson
Acclaimed Contributor
Solution

Re: Volume Group belongs to different CPU ID

It means exactly what it says. Vgimport has detected that this VG was originallly created on another system and you might be trying to use it on more than one host. This is a very common warning in a ServiceGuard environment, for example. It is a warning only and can be ignored unless you don't want this VG to be shared or activated among a group of hosts.

If this really bugs you, you can execute vgchgid BUT as soon as you try to vgimport on another host the mesage will reappear.

If it ain't broke, I can fix that.
James R. Ferguson
Acclaimed Contributor

Re: Volume Group belongs to different CPU ID

Hi:

The Volume Group ID (VGID) is composed of a system's unique id (as seen from 'uname -i') and the timestamp (in Epoch seconds) when the volume group was first created.

Your 'vgimport' is warning you that the volume belongs (or belonged) to another system.

Regards!

...JRF...
Sandman!
Honored Contributor

Re: Volume Group belongs to different CPU ID

Happens most likely when you're moving disks from one server to another. As the vgcreate(1M) command was run on a differenet server than the current one so the old/recorded VGID conflicts with the new/current VGID. Run vgchgid(1M) on each PV that belongs to this VG and try vgimport thereafter.
skt_skt
Honored Contributor

Re: Volume Group belongs to different CPU ID

thanks