vgcreate -e 38400 -p 32 -s 8 /dev/vg02 /dev/dsk/c8t0d1 Hung up!

[Joe Profaizer]

I'm on a Itanium system and created a 300GB lun and trying to create a new volume group to put the disk into. I ran the following commands up to the vgcreate command, and now it is hung up:

pvcreate /dev/rdsk/c8t0d1
mkdir /dev/vg02
mknod /dev/vg02/group c 64 0x020000

The above commands worked correctly, the next command is hung up. What can I do?

vgcreate -e 38400 -p 32 -s 8 /dev/vg02 /dev/dsk/c8t0d1


We have athe following versions of JFS.

JFS B.11.23 The Base VxFS File System
OnlineJFS B.11.23 Online features of the VxFS File System


The vgcreate command has been hung for about 1/2 hour now. Also receive the following error when using vgdisplay commands:
vgdisplay -v vg01

Cannot lock "/etc/lvmconf//lvm_lock" still trying ...


Please assist.

Thanks!!!

[Helen French]

1) "Cannot lock /etc/lvmconf/lvm_lock...." error is normal since one of your LVM command is already running. OS will create this lock file when a LVM command accessing /etc/lvmtab file so that no further LVM command will update it at the same time. Since your vgcreate is already running, it has already created the lock file so that your vgdisplay cannot create it until the first command is finished.

2) For your hanging problem, can you see any indication on the disk that it's being accessed? Do you have any disk errors on the system log files? Check your system process and see what's running (glance, top, sar). Also, make sure that you are up to date with patches.

[Sanjay_6]

Hi joe,

Maybe this will help you understand the error message.

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000063200620

The itrc doc id is KBRC00002639.

Hope this helps.

Regds

[Joe Profaizer]

Got answer from HP. There is a bug in ia64 with the command. See below:
Hello Joe, this is a known issue on Ia64 nodes,
vgcreate -e 38400 -p 32 -s 8 /dev/vg02 /dev/dsk/c8t0d1 --->
You may simply change the command to the follwing and it will work 1)you
will need to break-out (might need to reboot) 2)blow away /dev/vg02 with
#vgexport /dev/vg02 3)vgcreate -s 32M /dev/vg02 /dev/dsk/c8t0d1 (-e and -p
are optional and not
required)

[Jeff Schussele]

Hi Joe,

Well - I don't know if I'd accept that answer.
-e & -p *may* be optional but to me the -e is absolutely necessary - at least if you don't want to have to rebuild the VG down the road if you add a larger LUN/disk to this VG.
And then what are you going to do when you want to add the 17th PV to the VG? That's right - rebuild the VG again. So the -p *could* be critical as well. Sheesh I'm surprised they didn't tell you to live with a 4MB extent as well.....
I's be telling them to fix the damn bug ASAP!

My 2 cents,
Jeff