vgcreate: Cannot open the control file

[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

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

should i create the VG using -f option?

please suggest
thanks
vipin

[Vipin Singhal]

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

[Muthukumar_5]

0x720000 is hexa decimal only. 0x prefix is saying that the number is hexadecimal.

More than that, minor and major device number can be in hexa decimal or decimal too.

hth.

[Luk Vandenbussche]

Hi,

What is your maxvgs kernel parameter?

cat /stand/system | grep maxvgs ?

[Vipin Singhal]

#cat /stand/system
tunable maxvgs 80

[Vipin Singhal]

all permission ,owner,groups of group file 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

should i create the VG using -f option?

please suggest
thanks
vipin

[melvyn burnard]

why use 72?
that is in Hex, which relates to 114 decimal
Why not try something like 0x2c0000 (I do not see that in your list)

[Muthukumar_5]

Is this your thread? http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=975294

You've used -f option with vgcreate. Did you see the usage,

-f This option will force a volume group to be
created with a physical volume which has
alternate block(s) already allocated, (i.e.
this physical volume was not initialized
using pvcreate -f.) This option should be
used with extreme caution. If the volume
group to be created has a different physical
extent size, the alternate block(s) might be
inside the user data area. Potential data
corruption could occur.

It may give corruption on data. Be cautious.

hth.

[Vipin Singhal]

How i will change the minor no.

# mknod /dev/vg72/group c 64 0x2c0000
mknod: File exists
# cd /dev/vg72
# ll
total 0
crw-r--r-- 1 root sys 64 0x720000 Nov 16 01:35 group

I was trying to change it from 72 to 2c

thanks
vipin

[saju_2 · Accepted solution]

Hi

Remove the existing group file by rm command
rm /dev/vg74/group

Create new group file by

mknod /dev/vgxx/group c 64 0x2c0000

Regards
CS

[Muthukumar_5]

You've create lots of device files with mknod? remove the unneeded devices by using rm -rf /dev/vg. Create again with mknod command.

You can use 0x010000 for minor number as,

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

hth.

[Vipin Singhal]

thanks
i created the VG by your help

i need 75 GB for my file system.

these are the details:
# vgdisplay -v /dev/vg72
--- Volume groups ---
VG Name /dev/vg72
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 0
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 9215
VGDA 2
PE Size (Mbytes) 4
Total PE 9214
Alloc PE 0
Free PE 9214
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0


--- Physical volumes ---
PV Name /dev/dsk/c26t6d0
PV Name /dev/dsk/c29t6d0 Alternate Link
PV Status available
Total PE 9214
Free PE 9214
Autoswitch On

# diskinfo /dev/rdsk/c26t6d0
SCSI describe of /dev/rdsk/c26t6d0:
vendor: DGC
product id: CX700WDR10
type: direct access
size: 37748736 Kbytes
bytes per sector: 512
# diskinfo /dev/rdsk/c29t6d0
SCSI describe of /dev/rdsk/c29t6d0:
vendor: DGC
product id: CX700WDR10
type: direct access
size: 37748736 Kbytes
bytes per sector: 512

I think , i got 36.8Gb space using these two devices.
should i add more devices in this VG

[saju_2]

Hi

Yes u have 36 GB in this VG. If u want more space in this vg, add more disks intothis VG.

Allocate a disk to this server
ioscan -fnC disk
insf
pvcreate /dev/rdsk/cxtxdx
vgextend /dev/vg72 /dev/dsk/cxtxdx


Then create the LV's in the VG, with the required size

lvcreate (additional options) -L (size in MB) -n (name) /dev/vg72

newfs -F vxfs -o largefiles /dev/vg72/r

mount /dev/vg72/lvolx

This will give a a filesystem mounted at
Regards
CS

[Vipin Singhal]

hi,
I am adding one more device- c23t6d0 in vg72.

#pvcreate -f /dev/rdsk/c23t6d0
#vgextend /dev/vg72 /dev/dsk/c23t6d0
Current path "/dev/dsk/c29t6d0" is an alternate link, skip.
vgextend: Couldn't install the physical volume "/dev/dsk/c23t6d0".
The physical volume has no driver configured.

what should i do?
should i give this command-
#vgextend /dev/vg72 /dev/dsk/c29t6d0 /dev/dsk/c23t6d0

[Vipin Singhal]

Please suggest me

[Muthukumar_5]

Yes.

Try like,

#vgextend /dev/vg72 /dev/dsk/c29t6d0 /dev/dsk/c23t6d0

Refer vgextend man page for examples.

hth.

[melvyn burnard]

I would suggest now might be a good time to read the man pages and maybe also the manuals?

man vgcreate
man vgextend

[Muthukumar_5]

Refer manuals:

http://docs.hp.com/en/B2355-90672/ch03.html
http://www.experts-exchange.com/Operating_Systems/Unix/Unix_Setup/Q_21242092.html

hth.

[Vipin Singhal]

I typed wrong minor no., it should be in hexadecimal