1829904 Members
1608 Online
109993 Solutions
New Discussion

mknod vg10 +

 
SOLVED
Go to solution
Rob O'Connor
Advisor

mknod vg10 +

Quick question on mknod for vg10. Will the command be the following:

mknod /dev/vg10/group c 64 0x100000

Thank you.

H
5 REPLIES 5
melvyn burnard
Honored Contributor
Solution

Re: mknod vg10 +

no, these numbers are in hex, so assuming you have vg09 as 0x090000, then vg10 would be 0x0a0000; and
0x100000 would be vg16

You may need to increase you maxvgs kernel parameter, as it is defaulted to 10 if I remember, and you may have a problem adding in the 11th vg if this is so.

My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Bryan D. Quinn
Respected Contributor

Re: mknod vg10 +

You could use that possibly, if not already used but to stay in sequence I would recommend using 0a

VG Min #
00 00
01 01
02 02
03 04
05 05
06 06
07 07
08 08
09 09
10 0a
11 0b
12 0c
13 0d
14 0e
15 0f
16 10

Hope this helps!
-Bryan
Patrick Wallek
Honored Contributor

Re: mknod vg10 +

It could be, but if you want the minor number to be consistent with the VG# then you should use

# mknod /dev/vg10/group c 64 0x0a0000

Remember that the minor number is in Hexadecimal (Hex) format so a decimal 10 = a in hex. A hex 10 would be a decimal 16.

If you want to use a hex 10 as the minor number you might have to change the max_vgs kernel parameter, which I believe defaults to 10.
James R. Ferguson
Acclaimed Contributor

Re: mknod vg10 +

Hi:

Melvyn is correct. Also, make sure that your 'maxvgs' kernel paramter is sufficiently large. The default value is ten (10).

Regards!

...JRF...
Rob O'Connor
Advisor

Re: mknod vg10 +

Thanks everyone for prompt response. Bryan the chart helped mucho.

H