topic vgdisplay error in Operating System - HP-UX

vgdisplay error

Bonnie Kay Ornitz — Thu, 21 Mar 2002 18:38:06 GMT

Hi. We have a v-class server running 11.0 and ServiceGuard and I received the following error when running "vgdisplay /dev/vg00"

Couldn't query volume group "/dev/vg00". Possible error in the volume group minor number; Please check and make sure the group minor number is unique.

I verified that the minor number of the group file is unique (0x000000) and also destroyed and recreated it with the mknod command just to play safe and rule out corruption. Any ideas or suggestions would be greatly appreciated. Please email to bonnie.ornitz@wellpoint.com.

Thanks in advance,
Bonnie

Re: vgdisplay error

Jon Mattatall — Thu, 21 Mar 2002 19:09:44 GMT

Without SG, you could just :

mv /etc/lvmtab /etc/lvmtab.sav
vgscan -v (to recreate lvmtab)

Since you have SG, you'll have to move the /dev/slvmvg as well.

First, try strings /etc/lvmtab to check names,
and take a look at Alex Glennie's suggestion in

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x907637f45ef7d4118fef0090279cd0f9,00.html

for SG-specific tips.

This is the most common cure for your error.

HTH

Jon

Re: vgdisplay error

pap — Thu, 21 Mar 2002 19:17:35 GMT

Hi,
Please post the output of
#ll /dev/vg00

and # vgdisplay /dev/vg00

Thanks,
-pap

Re: vgdisplay error

Bonnie Kay Ornitz — Thu, 21 Mar 2002 19:46:52 GMT

ll /dev/vg00 output:

brw-r----- 1 root sys 64 0x00000d Dec 13 1998 controlm
crw-r----- 1 root sys 64 0x000000 Mar 21 07:43 group
brw-r----- 1 root sys 64 0x00000a Dec 9 17:45 lvcrash
brw-r----- 1 root sys 64 0x00000b Dec 9 17:45 lvdiamond
brw-r----- 1 root sys 64 0x00000e Dec 9 17:45 lvmfcobol
brw-r----- 1 root sys 64 0x00000f Dec 9 17:45 lvmfcobol2
brw-r----- 1 root sys 64 0x000007 Dec 9 17:45 lvopt
brw-r----- 1 root sys 64 0x000002 Jun 23 1998 lvpswap
brw-r----- 1 root sys 64 0x000003 Jun 23 1998 lvroot
brw-r----- 1 root sys 64 0x00000c Dec 13 1998 lvsas
brw-r----- 1 root sys 64 0x000001 Mar 21 01:18 lvstand
brw-r----- 1 root sys 64 0x000008 Jun 29 1998 lvswapa
brw-r----- 1 root sys 64 0x000009 Jun 29 1998 lvswapb
brw-r----- 1 root sys 64 0x000004 Dec 9 17:45 lvtmp
brw-r----- 1 root sys 64 0x000005 Dec 9 17:45 lvusr
brw-r----- 1 root sys 64 0x000006 Dec 9 17:45 lvvar
crw-r----- 1 root sys 64 0x00000d Nov 13 1998 rcontrolm
crw-r----- 1 root sys 64 0x00000a Jun 29 1998 rlvcrash
crw-r----- 1 root sys 64 0x00000b Mar 16 1999 rlvdiamond
crw-r----- 1 root sys 64 0x00000e Dec 11 2000 rlvmfcobol
crw-r----- 1 root sys 64 0x00000f Feb 18 2001 rlvmfcobol2
crw-r----- 1 root sys 64 0x000007 Jun 29 1998 rlvopt
crw-r----- 1 root sys 64 0x000002 Jun 23 1998 rlvpswap
crw-r----- 1 root sys 64 0x000003 Jun 23 1998 rlvroot
crw-r----- 1 root sys 64 0x00000c Oct 27 1998 rlvsas
crw-r----- 1 root sys 64 0x000001 Jun 23 1998 rlvstand
crw-r----- 1 root sys 64 0x000008 Jun 29 1998 rlvswapa
crw-r----- 1 root sys 64 0x000009 Jun 29 1998 rlvswapb
crw-r----- 1 root sys 64 0x000004 Jun 23 1998 rlvtmp
crw-r----- 1 root sys 64 0x000005 Jun 23 1998 rlvusr
crw-r----- 1 root sys 64 0x000006 Jun 23 1998 rlvvar

vgdisplay /dev/vg00 output:

vgdisplay: Couldn't query volume group "/dev/vg00".
Possible error in the Volume Group minor number; Please check and make sure the group minor number is unique.
vgdisplay: Cannot display volume group "/dev/vg00".

Well, it seems that the slvmvg file is easy enough to move, but moving lvmtab and running vgscan just isn't a possibility on our production system during the day. That would be a huge no-no and could cost me my job. We have several terabytes of data on this particular cluster.

We can schedule it during a down time. The lv's need to be quiet for this to run successfully. The real issue is why it happened. The slvmvg file has been around for ages and the vgdisplay problem only happened recently. If it's really a corruption to the lvmtab I'd like to know why!

Thanks again for all of your help.

Bonnie

Re: vgdisplay error

Roger Baptiste — Thu, 21 Mar 2002 20:37:43 GMT

hi,

check

ll /dev/*/group

and see whether there are minor numbers of VGs which are identical!

-raj

Re: vgdisplay error

pap — Thu, 21 Mar 2002 20:45:38 GMT

hi,
Can you post the out put of

#ll /dev/vg*

That will be helpful.
I forgot to ask that before.

-pap

Re: vgdisplay error

pap — Thu, 21 Mar 2002 20:53:49 GMT

Hi You can Run vgscan command in a preview mode using following.

#vgscan -p -v

This will give you the exact description about your problem.

There is no harm in using this command on production system as it will not going to update your lvmtab file.

-pap

Re: vgdisplay error

Bonnie Kay Ornitz — Thu, 21 Mar 2002 20:55:04 GMT