vgcreate failure

[Pete Randall]

Volker,

I'm always open to ideas - especially at a time like this.
ll /dev/*/group
crw-r----- 1 root sys 64 0x000000 Feb 14 2000 /dev/vg00/group
crw-rw-rw- 1 root root 64 0x010000 Jul 13 09:12 /dev/vg01/group
crw-rw-rw- 1 root root 64 0x020000 Jul 13 09:12 /dev/vg02/group
crw-rw-r-- 1 root sys 64 0x060000 Jul 19 14:59 /dev/vg20/group
crw-r--r-- 1 root sys 64 0x030000 Jun 27 2000 /dev/vgswap/group

maxvgs = 10

I don't think it's permissions, simply because the original 4 vg's have always had differences.

Pete

[MANOJ SRIVASTAVA]

Hi Pete


I also got this error in doing it on a EMC disk , waht was done to solve the problem was

pvcreate -f /dev/dsk/cxtydz.

and then vgcreate , this worked proplery.

Manoj Srivastava

[Pete Randall]

Manoj,

#mkdir /dev/vg20
# mknod /dev/vg20/group c 64 0x060000
# pvcreate -f /dev/rdsk/c18t1d2
Physical volume "/dev/rdsk/c18t1d2" has been successfully created.
# pvcreate -f /dev/rdsk/c18t1d3
Physical volume "/dev/rdsk/c18t1d3" has been successfully created.
# vgcreate /dev/vg20 /dev/dsk/c18t1d2 /dev/dsk/c18t1d3
Increased the number of physical extents per physical volume to 17326.
vgcreate: Volume group "/dev/vg20" could not be created:
Device busy

Pete

[Helen French]

Does this command shows any errors/warnings:

# vgdisplay -v

Is this LUN being used by anyother system ? What about the patches ?

[Helen French]

I would try another thing: First create the VG with one single disk and then add the other one with vgextend.

[Pete Randall]

Shiju,

No errors from vgdisplay -v.

Installed Mar 2002 quality pack a few weeks back.

I had successfully created this vg the other day but decided I didn't like the name I'd used, so I blew it away and re-created it with SAM. I then looked at it and didn't like SAM's choice of minor number so I manually removed the group file and did my own mknod. That was the start of my problems.

Pete

[Pete Randall]

Shiju,

vgcreate /dev/vg20 /dev/dsk/c18t1d3
Increased the number of physical extents per physical volume to 17326.
vgcreate: Volume group "/dev/vg20" could not be created:
Device busy

That's it for me - I'm going home and stick my head in a bucket of beer. We can resume this fascinating discussion on Monday.

Again - thanks to all and have a good weekend,

Pete

[Deshpande Prashant]

HI Pete
Give another try..

#vgcreate /dev/vg20
#vgextend /dev/vg20 /dev/dsk/c18t1d2

Thanks.
Prashant.

[Tom Maloy]

A bucket of beer sounds like an excellent choice for stress reduction.

You changed the minor number after you created the VG. That minor number might be stored away in some configuration file. Can you change it back to the original minor number, and then try to remove the VG?

Tom

[Sridhar Bhaskarla]

What I feel is that the /dev/vg99 directory got deleted before the volume group was actually exported. And during the later sequence, the PVs possibly lost their VGID information.

So, on your system, vg99 is still alive though there are no physical references to it.

Take a maintenance window and reboot the box. It should clear off the confusion that the system has been having and it will let you create the volume group fresh.

-Sri

[Wodisch_1]

You could try a "vgexport " on that VG first, but it might already be something wrong kept in kernel's memory about LVM - that would need a reboot, then :-(

Oh, cheers,
Wodisch

[Sridhar Bhaskarla]

Pete!!!...

I followed the other message in the thread and you said in one of them

"
and didn't like SAM's choice of minor number so I manually removed the group file and did my own mknod. That was the start of my problems. "

That might be the problem as the volume group was already active by the time you removed your group device. You would have recreated the group file and then exported the volume group to get rid of it.


-Sri

[Pete Randall]

Once again, thanks to all. It's Sunday morning and I just finished re-booting the machine into single user mode and running the pvcreate and vgcreate without any problems. It must have been that good long soak in the bucket of beer that did it! ;^)

Thanks,

Pete