1833959 Members
1980 Online
110063 Solutions
New Discussion

Re: VGCHDID problem

 
SOLVED
Go to solution
Fenny_1
Super Advisor

VGCHDID problem

Hi,
I am facing this error when im doing VGCHGID

vgchgid /dev/rdsk/c28t3d4
vgchgid: disk "/dev/rdsk/c28t3d4" is already in vg "/dev/BC1_xpvggendata5".

wat does that mean???
3 REPLIES 3
Denver Osborn
Honored Contributor
Solution

Re: VGCHDID problem

You need to change the id before importing and activating the volume group.

Before importing the volume group, run the vgchgid command for the business copy luns. Once that's done, do your vgimport.

To fix what you have now, deactivate the volume, vgexport, vgchgid then vgimport.

If this system only has access to the business copy, then you're fine to keep it as is without changing the vgid. Otherwise you'll end up with two VGs having disks that share the same id... which would cause problems w/ lvm.

-denver

Ninad_1
Honored Contributor

Re: VGCHDID problem

Hi,

The messages exactly tells you what the problem is.
There is a VG BC1_xpvggendata5 already imported on the server and which is using disk c28t3d4.
Do a strings /etc/lvmtab | grep c28t3d4 to reconfirm this.

Proabaly, you did not export the VGs for the BC before doing the BC synchronisation ?
Now you can do
ll /dev/BC1_xpvggendata5/group #[Note the minor number for the VG]
vgexport -v -p -m BC1_xpvggendata5.map /dev/BC1_xpvggendata5 # [To have the map file to be used when you do vgimport later ]
vgchange -a n /dev/BC1_xpvggendata5 #[Deactivate VG]
vgexport /dev/BC1_xpvggendata5 #[Export VG]
vgchgid /dev/rdsk/c28t3d4
mkdir /dev/BC1_xpvggendata5
mknod /dev/BC1_xpvggendata5/group c 64 0xNN0000 #[ Us the minor number noted earlier]
vgimport -m BC1_xpvggendata5.map /dev/BC1_xpvggendata5 /dev/dsk/c28t3d4
vgchange -a y /dev/BC1_xpvggendata5


Regards,
Ninad
Fenny_1
Super Advisor

Re: VGCHDID problem

Hi,
Thanks for everyone's valuable help. My problem resolved.