Operating System - HP-UX
1752664 Members
6016 Online
108788 Solutions
New Discussion юеВ

pvdisplay and diskinfo conflict

 
SOLVED
Go to solution
YMJ
Frequent Advisor

pvdisplay and diskinfo conflict

Hi all

we assigned 500 GB disk form EMC box to HP-UX rp74200 server. the problem we have here the server recognizes the disk as 100 GB not 500 GB.

mph01 #pvdisplay /dev/dsk/c24t8d5
Device file path "/dev/dsk/c24t8d5" is an alternate path
to the Physical Volume. Using Primary Link "/dev/dsk/c23t8d5".
--- Physical volumes ---
PV Name /dev/dsk/c23t8d5
PV Name /dev/dsk/c24t8d5 Alternate Link
VG Name /dev/vgora12
PV Status available
Allocatable yes
VGDA 2
Cur LV 2
PE Size (Mbytes) 32
Total PE 3236
Free PE 0
Allocated PE 3236
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On


diskinfo output:

mph01 #diskinfo /dev/rdsk/c23t8d5
SCSI describe of /dev/rdsk/c23t8d5:
vendor: EMC
product id: SYMMETRIX
type: direct access
size: 530323200 Kbytes
bytes per sector: 512


Is there limit on the disk? or need a patch?

Thanks for your help.
6 REPLIES 6
Mridul Shrivastava
Honored Contributor
Solution

Re: pvdisplay and diskinfo conflict

I think there were some disk present in the VG before you added this PV and they were of 1GB or lower size. What diskinfo is showing is correct and pvdisplay also shows the correct info.

Now it is required to increase the number of extents per PV. Please post the vgdisplay o/p so things will be clear.

Whats the OS version, based on that we could identify if vgmodify could be executed.
Time has a wonderful way of weeding out the trivial
YMJ
Frequent Advisor

Re: pvdisplay and diskinfo conflict

Hi Mridul

Yes, there were 100GB disks exist before.

mph01 #vgdisplay vgora12
--- Volume groups ---
VG Name /dev/vgora12
VG Write Access read/write
VG Status available, shared, server
Max LV 255
Cur LV 34
Open LV 34
Max PV 50
Cur PV 32
Act PV 32
Max PE per PV 3236
VGDA 64
PE Size (Mbytes) 32
Total PE 103552
Alloc PE 103552
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

I can see "Max PE per PV" = 3236 which limit the size. Is there a way to increase this number? or need to recreate the VG?

Thanks,
Mridul Shrivastava
Honored Contributor

Re: pvdisplay and diskinfo conflict

vgmodify comes with 11.31 per default and for 11.23 per patch.

The procedure is as follows

- check
- preview
- assign new values

see

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01920387/c01920387.pdf (BSC link updated by admin)

If you have a lower version and don't want to go for vgmodify then the only option left is to recreate the VG. Make sure that you create VG using the biggest disk or assign the higher max PEs and make sure that u change the value of PE size as well. For details refer man pages of vgcreate.
Time has a wonderful way of weeding out the trivial
Aneesh Mohan
Honored Contributor

Re: pvdisplay and diskinfo conflict

sounds like the problem with the max_pe .You can set using -e option .For existing vg you can modify this parameter using vgmodify command(only for 11.23 and 11.31) and for new volume group you can specify this along with vgcreate.

-e max_pe


Set the maximum number of physical extents that can be allocated from any of the physical volumes in the volume group (see vgcreate(1M)) -e).

The maximum number of physical extents can range from the current highest physical extent in use on any physical volume in the volume group (1 if none in use) up to 65535.
Jeeshan
Honored Contributor

Re: pvdisplay and diskinfo conflict

HI


I think its related to max PE per PV parameter.

Coz when you vgcreate the -e option let you permit to add more PVlater on.

in your scenarion it's only permits 3236 PE.

Add another VG and set its -e option to specify more size.
a warrior never quits
YMJ
Frequent Advisor

Re: pvdisplay and diskinfo conflict

Thank you all for the help

since the only solution is to recreate the VG with more PE per PV which is not possible in my case, I need to remove the lun and add it with 100 G

Thanks,