VGIMPORT with MC Service Guard

[Wina A. Buenavista]

Hi,
Please help, this is the error I received during vgimport in Node2, "volume Group /dev/vgsap4 is still active". To be clearer, here are the details of what I have done:

at NODE1
1. cmhaltpkg -v sapdbci
2. cmhaltcl -v
3. creatd volume group "/dev/vgsap4" with 10 lvs.
4. vgchange -a n /dev/vgsap4
5. vgexport -p -s -v -m /tmp/sap4.mapfile /dev/vgsap4
6. put sap4.mapfile to NODE2

AT NODE2
1. mkdir /dev/vgsap4
2. mknod /dev/vgsap4/group c 64 0x070000
3. vgimport -s -m /tmp/sap4.mapfile /dev/vgsap4

thanks.

[linuxfan]

Hi Wina,

Is this a new VG you are creating on node 2?

Make sure you are using a unique minor number when creating the group file
ll /dev/*/group

You are using 0x070000 (make sure there isn't another VG with the same minor number)

-Ramesh

[Wina A. Buenavista]

yes this is a new VG at NODE2.
the minor number is already unique. but stil got the same error.

any other suggestion? thanks.

[linuxfan · Accepted solution]

Hi Wina,


That is strange, the only time i would see this if there is a duplicate minor number or if you were trying to import an already existing VG.

I know sounds silly(since you are just creating this VG) but make sure the VG doesn't exist already (strings /etc/lvmtab |grep vgsap4) and also do a "vgdisplay /dev/vgsap4"
-Ramesh

[Sanjay_6]

Hi,

The only thing it looks like is that the VG somehow got activated on Node1 again. Can you try and deactivate it once again and try importing the VG again on Node2. Since the VG directory on node2 has been recently created that means you didn't had that Vg earlier on that system.

This is puzzling, as the procedure you have follows after creating the VG on Node1 and exporting and importing the VG is correct. You should not be getting any errors.

Hope this helps.

thanks

[Wina A. Buenavista]

thanks a lot ... you were right, we have ovelooked duplicate minor in one of our vgs.
Until next time, wina :-)