vg create failed

[CJENSEN_1]

Getting the following error when trying to create a new volume group. Complains about the minor number not being unique. I'm attaching a screenshot of the error message. Thanks.

[Ivan_86]

Hi..!!

Verify that the minor number its no duplicate

cd /dev
ll vg* | grep group

Review taht numner hexadecimal ints no duplicate

[CJENSEN_1]

It is in fact a duplicate. However, I'm doing this through SAM - should not SAM take care of this? (Never had this problem before). What do I need to do to clear out the vg info?
1) move /etc/lvmtab to /etc/lvmtab.kill
2) do a vgscan -v
Anything else?

[CJENSEN_1]

I've removed the old vg information. Now, when I try to re-create it, I get the following error: cannot open the control file.....
Please see the attachment.
Thanks.

[Devender Khatana]

Hi,

A better option will be to do the same from command line. First identify the disk or disks on which you want to create the VG.

Now note down the next available minor number for new VG in hex by

#ll /dev/*/group

Suppose the number you got is 0x0f0000 as next available number and /dev/dsk/cxtydz as the disk on which you are creating the VG. Also note down the size of disk.

#mkdir /dev/vgname

#mknod /dev/vgname/group c 64 0x0f0000

#pvcreate /dev/rdsk/cxtydz

#vgcreate -e 15000 -s 32 /dev/vgname /dev/dsk/cxtydz

Other options apart from this also can be provided.

#lvcreate -L(Size of LVOL in MB) /dev/vgname

#newfs -F vxfs /dev/vgname/lvol1

Repeat if required to create multiple file systems.

Create entry in /etc/fstab for new file systems.

HTH,
Devender

[Stuart Abramson]

I agree with Devender above. Learn to do this with commands.

It looks like you are getting vg16b and vg16g confused in your SAM screen shots.

Write down on a piece of paper all your VGs and all the minor numbers and pick one that is unique.

[Stuart Abramson]

Also, list your VGs with "vgdisplay" and then compare the list to a "ll /dev/*/group". It's possible that somebody created a VG and removed it somehow or started to create a VG and then left the "dev/vgname/group" file around and so you don't see the VG in a vgdisplay, but vgcreate will fail because the file already exists...

[Denver Osborn · Accepted solution]

This could indicate a problem with the maxvgs kernel parameter.

Please have a look at the maxvgs kernel parameter. The default value (10 I think) may either be set too low to add the new vg.

Can you also post the output from 'll /dev/*/group' and the value of maxvgs from 'kmtune -q maxvgs'.


-denver

[CJENSEN_1]

Thanks everyone for replying. Denver Osborne - your advice on the kernel 'maxvgs' was the root of my problems. It was set to 10. Bumping this up solved the problem. Points have been assigned. Thanks.

[CJENSEN_1]

Solution as per my previous post.