topic Vgimport issue!! in Operating System - HP-UX

Vgimport issue!!

Fenny_1 — Tue, 10 Apr 2007 10:53:20 GMT

Hi,
On node1 i exported a FS using this command
vgexport -p -v -s -m vgtib2data.map /dev/vgtib2data
It exported successfully but when i use that map file to import the VG information on Node2 it imported succssfully but in /etc/lvmtab the VG is missing a Physical volume. But i can find this Physical volume on node2 when i do ioscan.

On Node1 Strings /etc/lvmtab
/dev/vgtib2data
/dev/dsk/c19t0d3
/dev/dsk/c19t2d0

On node after doing an import /etc/lvmtab
/dev/vgtib2data
/dev/dsk/c19t0d3

When i issue this command
tppora50:/#vgimport /dev/vgtib2data/ /dev/dsk/c19t2d0
vgimport: Volume group "/dev/vgtib2data" already exists in the "/etc/lvmtab" file.

But it's not present in strings /etc/lvmtab

Please help me on this. Waiting for a quick response.

Thanx in advance

Re: Vgimport issue!!

Sundar_7 — Tue, 10 Apr 2007 10:58:42 GMT

How did you import the vg ? You cannot import a VG that is already in the /etc/lvmtab

in Node2

# rcp -p node1:/tmp/vgtib2data.map /tmp
# vgexport /dev/vgtib2data
# mkdir /dev/vgtib2data
# mknod /dev/vgtib2data/group c 64 0xNN0000
NN==Minor number of the VG
# vgimport -v -s -m /tmp/vgtib2data.map /dev/vgtib2data
# vgchange -a r /dev/vgtib2data
# vgcfgbackup /dev/vgtib2data
# vgchange -a n /dev/vgtib2data

Sundar.

Re: Vgimport issue!!

Fenny_1 — Tue, 10 Apr 2007 11:13:25 GMT

Hi Sundar,
I exported the VG first and then import it using the same commands which you mentioned in your email. But sumhow the Physical volume is not included on NODE /etc/lvmtab file.

Please help me to resolve this

Re: Vgimport issue!!

Steve Reynolds — Tue, 10 Apr 2007 11:58:06 GMT

Steps I do for this.

1. create map file from Node1
vgexport -pvs -m mapfile vgxx
2. copy map file to Nod2
3. vgchange -a n vgxx (Node 1)

4. On Node 2
mkdir /dev/vgXX
mknod /dev/vgxx/group c 64 0x(unique ID)
5. vgimport -vs -m (mapfile) /dev/vgxx
6. vgchange -a y /dev/vgxx
7. verify with vgdisplay -v vgxx

Having the same disk device files between
both nodes is unusual, not impossible.

Re: Vgimport issue!!

A. Clay Stephenson — Tue, 10 Apr 2007 12:04:35 GMT

It is rather unusual that you have the same device paths on both nodes but not impossible. Another thing to check is the uniqueness of the minor device number of the group node.

Do an "ls -l /dev/vg*/group" and make absolutely certain the all minor device numbers are unique on any given host. It's not necessary that the minor device numbers for /dev/vgXX be the same on nodeA and nodeB but it is absolutely necessary that each VG on any given host is unique for that host. If this rule is violated, chaos is assurred.

Re: Vgimport issue!!

Sundar_7 — Tue, 10 Apr 2007 12:06:22 GMT

If the -s option is used with vgimport, then the device files doesn't matter. Vgimport matches the VGID in the map file with the VGID in the disks that the system sees.

Is this a shared storage ?

# echo "0x2008?4D" | adb /dev/dsk/c19t0d3

# echo "0x2008?4D" | adb /dev/dsk/c19t2d0

Compare the output of the above commands. The output should match except for the PVID.

Re: Vgimport issue!!

David Bellamy — Tue, 10 Apr 2007 13:58:03 GMT

Make sure that both Nodes see the shared disk.

Re: Vgimport issue!!

Fenny_1 — Wed, 11 Apr 2007 10:25:21 GMT

Both nodes are getting the shared storage from EVA. And i checked with ioscan that the disk is there but when i import it it doesnt get included in the VG info in /etc/lvmtab