Operating System - HP-UX
1833770 Members
2692 Online
110063 Solutions
New Discussion

Total PE / Allocated PE mismatch !!!

 
SOLVED
Go to solution
Venky_1
Frequent Advisor

Total PE / Allocated PE mismatch !!!

Hi ,

Even though there are no logical volumes defined in the VG, but still there is a mismatch in the Total PE and Allocated PE.
Please see the output of the "vgdisplay of the problematic VG.

Any suggestions.

Thanks
Venky
==========================================
Max LV 255
Cur LV 1
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4341
VGDA 2
PE Size (Mbytes) 4
Total PE 4340
Alloc PE 1024
Free PE 3316
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
==============================================
Winners never quit and quitters never win
14 REPLIES 14
Pete Randall
Outstanding Contributor

Re: Total PE / Allocated PE mismatch !!!

Venky,

It also says "Cur LV 1", indicating that a logical volume has been defined. Does a "vgdisplay -v" command show you any logical volumes. If not, I would do a vgexport on this VG and recreate it.


Pete

Pete
Ken Hubnik_2
Honored Contributor

Re: Total PE / Allocated PE mismatch !!!

What do you get from doing a strings on your lvmtab

strings /etc/lvmtab
Ken Hubnik_2
Honored Contributor

Re: Total PE / Allocated PE mismatch !!!

Can you post the output from vgdisplay -v /dev/vgxx
Massimo Bianchi
Honored Contributor

Re: Total PE / Allocated PE mismatch !!!

Hi,
can you post also a "pvdiplay -v" of each disk in the VG ?

What looks more strange to me is the mismatch between

Cur LV 1
Open LV 0


Massimo
Elena Leontieva
Esteemed Contributor

Re: Total PE / Allocated PE mismatch !!!

If you are in a ServiceGuard environment, see the Document id: KBRC00010801
Venky_1
Frequent Advisor

Re: Total PE / Allocated PE mismatch !!!

Hi ,

Please see the output of "vgdisplay -v
It doesn't show any logical volumes defined in this VG.
==============================================
VG Status available
Max LV 255
Cur LV 1
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4341
VGDA 2
PE Size (Mbytes) 4
Total PE 4340
Alloc PE 1024
Free PE 3316
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0


--- Physical volumes ---
PV Name /dev/dsk/c2t2d0
PV Status available
Total PE 4340
Free PE 3316
Autoswitch On
===============================================
Winners never quit and quitters never win
Pete Randall
Outstanding Contributor

Re: Total PE / Allocated PE mismatch !!!

Venky,

In that case, I would re-define the VG. First, run vgexport to remove it, then go through your usual creation via SAM or command line.


Pete

Pete
Venky_1
Frequent Advisor

Re: Total PE / Allocated PE mismatch !!!

Hi ,

Please see the output of the "vgexport -v

=========================================
Beginning the export process on Volume Group "/dev/vgroot".
vgexport: Volume group "/dev/vgroot" is still active.
vgexport: Couldn't export volume group "/dev/vgroot".
=======================================
Thanks
Venky
Winners never quit and quitters never win
Massimo Bianchi
Honored Contributor

Re: Total PE / Allocated PE mismatch !!!

Hi,
in addition to Pete's, i would do a good
"pvcreate -f" of the disk, i think there might be something wrong that is reporting used PE.

Is there any file in the /dev/vg* ? Maybe there is conflict with the minor of another VG or something similar.

HTH,
Massimo
James R. Ferguson
Acclaimed Contributor
Solution

Re: Total PE / Allocated PE mismatch !!!

Hi:

You must deactivate the volume group if you want to 'vgexport' it:

# vgchange -a n /dev/vgname
# vgexport /dev/vgname

Regards!

...JRF...
Patrick Wallek
Honored Contributor

Re: Total PE / Allocated PE mismatch !!!

The VG has to be deactivated before you can vgexport it.

# vgchange -a n /dev/vgroot

# vgexport /dev/vgroot
Jean-Louis Phelix
Honored Contributor

Re: Total PE / Allocated PE mismatch !!!

Hi,

I can't see the mismatch (perhaps I'm too tired :-) )

Total = Free + Alloc (4340 = 3316 + 1024)

So you've created a 1Go lvol, but the special files have disapeared. You can try the vgexport/vgimport tip (but first deactivate the vg using vgchange -a n vgxx), or simply try to recreate the special files using mknod, but you have to know the number of the lvol. Try with number 1 and if it doesn't work try with next ...

mknod /dev/vgxx/lvolY b 64 0xNN000Y
mknod /dev/vgxx/rlvolY c 64 0xNN000Y

where Y is the lvol number and NN is the vg number same as what you can get using 'll /dev/vgxx/group"

Check result using vgdisplay -v vgxx. If lvol size is 0, then you've chosen a wrong lovol number, rm both files and try next ...

Regards.
It works for me (© Bill McNAMARA ...)
Justin Willoughby
Regular Advisor

Re: Total PE / Allocated PE mismatch !!!


I had this problem once. It was fixed by simply de-activating and re-activating the volume group. I was moving LV from one disk to another. When I had the application down I just did a

vgchange -a n vgname
vgchange -a y vgname
vgdisplay -v vgname

All set, at least for my problem.

- Justin
Werner Buckens
Occasional Advisor

Re: Total PE / Allocated PE mismatch !!!

As mentioned above the vgdisplay information gives back that there is a logical volume. I guess that the VGDA is corrupt or something. If you want to re-create the VG, follow these steps:

First drop the VG
# cd /
# vgchange ???a n
# vgexport

Re-create the VG
# pvcreate ???f /dev/rdsk/c2t2d0
# mkdir /dev/
# mknod /dev//group c 64 0xNN0000
where the n stands for a free and unique (!!) minor-number among all other existing VG???s. NN runs from 00 to 09
# vgcreate ???s 4 /dev/ /dev/dsk/c2t2d0

This should do the trick for you.