topic Re: cannot vgcreate - urgent in Operating System - HP-UX

cannot vgcreate - urgent

Tonny Sejr Kromann — Thu, 27 Mar 2003 19:14:51 GMT

Hi
I have to move data to free up at XP256 by tomorrow. So I must make new vg's on the new XP512. But somehow vgcreate isn't polite to me. Could someone please help?

# vgcreate vg20DFSInf /dev/dsk/c12t13d4
vgcreate: Cannot open the control file "/dev/vg20DFSInf/group":
No such device
# ll /dev/vg20DFSInf/group
crw-rw-rw- 1 root sys 64 0x200000 Mar 27 19:54 /dev/vg20DFSInf/group

The disk is recognized with xpinfo and I have succesfully pvcreated it. But still it doesnt work. any suggestions?

--
Best regards
Tonny

Re: cannot vgcreate - urgent

Sridhar Bhaskarla — Thu, 27 Mar 2003 19:19:32 GMT

Hi Tonny,

Your group file is incorrect.

Minor number 200000 is valid only if your maxvgs kernel parameter is specified more than 32. Look at the command 'kmtune -l -q maxvgs' and find the value.

The hex equivalent of the two digits followed by 0x in the minor number should be equal or less than the "maxvgs" parameter.

If this is only the second volume group, then you might want to create a group file like

mknod /dev/vg20DFSInf/group 0x020000

Otherwise, increase the maxvgs parameter and that needs a reboot.

-Sri

Re: cannot vgcreate - urgent

Patrick Wallek — Thu, 27 Mar 2003 19:20:35 GMT

It looks like your group file is incorrect.

What is the minor number supposed to be? If it is supposed to be 2, then do the following:

# rm /dev/vg20DFSInf/group

# mknod /dev/vg20DFSInf/group c 64 0x020000

If the minor number is supposed to be 20, do the following:

# rm /dev/vg20DFSInf/group

# mknod /dev/vg20DFSInf/group c 64 0x140000

Remember that the minor number is a HEXADECIMAL value thus a decimal 20 = a hex 14

Also make sure that your MAXVGS kernel parameter is set high enough to allow this.

By default MAXVGS is 10 or 12. If you want a minor number that is larger than that you will need to increase maxvgs, regen the kernel and reboot the machine.

Re: cannot vgcreate - urgent

Ron Cornwell — Thu, 27 Mar 2003 19:22:05 GMT

Try creating the vg with a different name. I believe the group file should not exist until after the vg is created. This would be a good test. If it is true you can vgremove the one just created if you want to keep the old name and rm -r /dev/vg20DFSInf before creating the vg with the name vg20DFSInf.

Re: cannot vgcreate - urgent

S.K. Chan — Thu, 27 Mar 2003 19:22:34 GMT

Use a smaller minor number ..
# mknod /dev/vg20DFSInf/group c 64 0x040000
for example (as long as they are unique). If you use 0x20, you might be working against the max volume group limit (ie 15 by default).

Re: cannot vgcreate - urgent

Ross Zubritski — Thu, 27 Mar 2003 19:23:14 GMT

Sri- is right on the money (as usual) with this one!

Regards,

RZ

Re: cannot vgcreate - urgent

Tonny Sejr Kromann — Thu, 27 Mar 2003 19:27:30 GMT

Yes I surely did have too many zeroes in there. Thanks to all :)

--
Best regards
Tonny