- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- pvdisplay and diskinfo conflict
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2008 11:08 PM
тАО04-11-2008 11:08 PM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2008 12:08 AM
тАО04-12-2008 12:08 AM
SolutionNow 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2008 12:50 AM
тАО04-12-2008 12:50 AM
Re: pvdisplay and diskinfo conflict
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,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2008 12:56 AM
тАО04-12-2008 12:56 AM
Re: pvdisplay and diskinfo conflict
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2008 12:57 AM
тАО04-12-2008 12:57 AM
Re: pvdisplay and diskinfo conflict
-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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2008 01:15 AM
тАО04-12-2008 01:15 AM
Re: pvdisplay and diskinfo conflict
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2008 03:49 AM
тАО04-12-2008 03:49 AM
Re: pvdisplay and diskinfo conflict
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,