vgimport

[jamshed]

When I try to import my volume group to another node next message appeared.

Importing Volume Group vgu09 with minor number 0x0a0000 on host hp02
vgimport: Cannot open the control file "/dev/vgu09/group":
No such device
But this volume exist in first node and accurately working

[Bharat Katkar]

HI Jamshed,
While importing VG vgu09 you have to follow followign procedure.

On Node1:

1. Note down the minor no. of /dev/vgu09/group. e.g. it is 0x020000
2. Do vgexport ( use -p) e.g. map file is vgu09.map
3. ftp vgu09.map to node2 in /tmp

On Node2
1. mkdir /dev/vgu09
2. mknod /dev/vgu09/group c 64
3. vgimport -v -m /tmp/vgu09.map vgu09

That's all.
It works.
Regards,

[Michael Tully]

Please advise your exact procedure being used.

At first guess, it could be that you have exceeded the allowed number of volume groups allowed in your kernel (maxvgs) even allowing for the fact your probably running MC/SG

[jamshed]

This step was for importing
vgexport -p -s -m /etc/cmcluster/vgs/vgu09.map vgu09
mkdir /dev/vgu09
/usr/sbin/mknod /dev/vgu09/group c 64 0x0a0000
/usr/sbin/vgimport -s -m /etc/cmcluster/vgs/vgu09.map vgu09

but situation is still same

[Michael Tully · Accepted solution]

Please verify the number of volume groups allowed:

kmtune -l -q maxvgs (kernel setting)
You may have exceeded the attempted number.

[Gary L. Paveza, Jr.]

Just a note, but the maxvgs kernel parameter does NOT indicate the maximum number of volume groups you can have (which would be intuitive IMHO), but rather the maximum value that can be used for the minor number. From your example, you are using 0x0a as the minor number - which equates to a decimal 10. Check that your maxvgs parameter is at least 10. Also that 0x0a is not already in use (easiest way is ll /dev/vg*/group.