HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: changing a VG's 'max_pe' value
Operating System - HP-UX
1837523
Members
3386
Online
110117
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
10-27-2001 03:30 PM
10-27-2001 03:30 PM
Hi All,
I recently added a new lun to a volume group and was informed that while the physical volume contained 2559 physical extents, the max_pe for that VG was 2500, therefore it would only use that smaller #.
Is there a way to modify that value for the volume group? I can only see how to set it when vgcreate'ing.
In what scenario would you want to limit the amount of PE's allocatable to a VG - you can only assign a PV to a single VG, right? It's not like you could use the unused PE's in another VG...
Cheers,
Mark
I recently added a new lun to a volume group and was informed that while the physical volume contained 2559 physical extents, the max_pe for that VG was 2500, therefore it would only use that smaller #.
Is there a way to modify that value for the volume group? I can only see how to set it when vgcreate'ing.
In what scenario would you want to limit the amount of PE's allocatable to a VG - you can only assign a PV to a single VG, right? It's not like you could use the unused PE's in another VG...
Cheers,
Mark
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2001 06:06 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2001 05:29 AM
10-28-2001 05:29 AM
Re: changing a VG's 'max_pe' value
Hi Mark:
The values of 'max_pe', 'max_pv', 'pe_size' and 'max_lv' are fixed at 'vgcreate' and cannot be changed unless the volume group is recreated from scratch.
'max_pe' is set to 1016 or the the number of physical extents in the largest disk used in the 'vgcreate' process. See the 'vgcreate' man pages for more details.
The 'max_pe' value is used to calculate the physical-to-logical extent mapping information kept in the VGRA. It is written to the disk first, and then data afterwards, so there is no provision to expand this mapping.
Stated differently, the size of the LVM structures must fit into one physical extent. Thus, different geometries can be found by varying 'pe_size', 'max_pv', 'max_lv' and 'max_pe'. In many cases, this means carefully choosing these values at the time of the 'vgcreate', and may mean incrasing the value of 'pe_size'.
Regards!
...JRF...
The values of 'max_pe', 'max_pv', 'pe_size' and 'max_lv' are fixed at 'vgcreate' and cannot be changed unless the volume group is recreated from scratch.
'max_pe' is set to 1016 or the the number of physical extents in the largest disk used in the 'vgcreate' process. See the 'vgcreate' man pages for more details.
The 'max_pe' value is used to calculate the physical-to-logical extent mapping information kept in the VGRA. It is written to the disk first, and then data afterwards, so there is no provision to expand this mapping.
Stated differently, the size of the LVM structures must fit into one physical extent. Thus, different geometries can be found by varying 'pe_size', 'max_pv', 'max_lv' and 'max_pe'. In many cases, this means carefully choosing these values at the time of the 'vgcreate', and may mean incrasing the value of 'pe_size'.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2001 03:41 PM
10-28-2001 03:41 PM
Re: changing a VG's 'max_pe' value
Mark,
Please read this Document:
**KBRC00004285** (it explains it all!)
The basic reason for these restrictions is
VGDA (which needs to be in every disk of the
VG) cannot be larger than the size of one
extent. So, if you set a large number
of PE extent during the VG creation, it would
mean a larger VGDA, which means the Extent size
will increase!!, since it has to house the
mapping of a larger number of extents.
So, you have to choose between balancing
the maximum number of PV's/PE's/PE size.
Two other useful documents to refer to:
Docid: KBRC00001020
DocId: KBRC00000244
HTH
raj
Please read this Document:
**KBRC00004285** (it explains it all!)
The basic reason for these restrictions is
VGDA (which needs to be in every disk of the
VG) cannot be larger than the size of one
extent. So, if you set a large number
of PE extent during the VG creation, it would
mean a larger VGDA, which means the Extent size
will increase!!, since it has to house the
mapping of a larger number of extents.
So, you have to choose between balancing
the maximum number of PV's/PE's/PE size.
Two other useful documents to refer to:
Docid: KBRC00001020
DocId: KBRC00000244
HTH
raj
Take it easy.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP