different outputs from pvdisplay & pvcreate

[Bharat Katkar]

Hi Vipin,
Some more details on group file.

Group file is the group special file which acts as VG control file and it's major no is always 64.
Suppose we have minor no as 0x720000 then from left side:

0x indicates it's hex no.
72 indicates VG number which has to be unique in a System
0000 this number's are always zero (not used by group file)

The only concern is the no. 72. You have to make sure that this does not belong to any other VG in the system.

Now once you have created group file and VG then you go on creating lv's into it, then the last four digits which were zero in case of group file are used as:

0x720001,0x720002 and so on...
Now here rightmost two digit indicates lv number in vg no 72. Two digits between VG number and lv no remains unused.

Finally, now if i confirm that 72 is free to use and no other vg with no 72 exists then i would proceed as below for creating vg vg72:

mkdir /dev/vg72
mknod /dev/vg72 c 64 0x720000
vgcreate vg72

Now when i create lv into this VG then there are automatically assigned minor number as:
0x720001, 0x720002, and so on.

Hope that helps.
Regards,

[Vipin Singhal]

i have given these commands:

#pvcreate /dev/rdsk/c26t6d0
#pvcreate /dev/rdsk/c29t6d0
#mkdir /dev/vg72
#mknod /dev/vg72/group c 64 0x720000
#vgcreate /dev/vg72 /dev/dsk/c26t6d0

vgcreate: Cannot open the control file "/dev/vg72/group":
No such device

Please suggest what should i do?

these are the list of this command:

# ll /dev/vg*/group |awk '{print$6}'
0x000000
0x040000
0x050000
0x060000
0x070000
0x080000
0x090000
0x100000
0x110000
0x120000
0x130000
0x140000
0x150000
0x160000
0x170000
0x180000
0x190000
0x200000
0x210000
0x220000
0x230000
0x240000
0x250000
0x260000
0x270000
0x280000
0x290000
0x300000
0x310000
0x320000
0x330000
0x340000
0x350000
0x360000
0x370000
0x380000
0x390000
0x400000
0x410000
0x420000
0x430000
0x440000
0x450000
0x460000
0x470000
0x480000
0x490000
0x3a0000
0x3b0000
0x3c0000
0x3d0000
0x3e0000
0x3f0000
0x1f0000
0x2a0000
0x1a0000
0x1b0000
0x1c0000
0x1d0000
0x1e0000
0x2b0000
0x720000

[saju_2]

Hi

Check the below theread

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=574955

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=48788
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=3356

Issue with the maxvg parameter in kernel./

Regards
CS

[Vipin Singhal]

should i use again:
#vgcreate -f /dev/vg72 /dev/dsk/c26t6d0

with using -f option

note: i have created LV with -f option

[Vipin Singhal]

should i use again:
#vgcreate -f /dev/vg72 /dev/dsk/c26t6d0

with using -f option

note: i have created LV with -f option


or should i use again:

#mknod /dev/vg72/group c 64 0x720000

with hexadecimal no.

what will be the hexadecimal no. for minor no. 0x720000

thanks
vipin

[Bharat Katkar]

Hi Vipin,

do:

# cd /dev/vg72
# ll /dev/vg72/group

What does it display, it should show you:

crw-r----- 1 root sys 64 0x720000 Sep 20 05:35 group

Please check the permission/owner/group accordingly

Regards,

[Vipin Singhal]

yes,
all permission .owner,groups are ok , i compared these things from other group file of different VG.

I also tried to create new VG74
same problem with VG74 group file

crw-r--r-- 1 root sys 64 0x740000 Nov 16 02:40 group

# vgcreate /dev/vg74 /dev/dsk/c26t6d0
vgcreate: Cannot open the control file "/dev/vg74/group":
No such device

please suggest

[Vipin Singhal]

should i create the VG using -f option?

[Vipin Singhal]

i used this command
#pvcreate -f /dev/dsk/c26t6d0
to create LV

[David Bellamy]

Vlpin check that you haven't hit maxvg. When you are doing a vgcreate and you receive the message "can not open control file" it means that the unique id has exceeded the number for maxvg. 72 in hex I believe translate into 114 in decimal .