- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Cannot vgmodify VG after pvmove-ing extent zero
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
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
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
10-14-2011 01:48 AM
10-14-2011 01:48 AM
Cannot vgmodify VG after pvmove-ing extent zero
Hi
I have increased 1 LUN on an EVA from 400 to 500GB. The vgmodify review is showing the the MAX_PE_PER_PV parametrer is not large enough.
Below is a vgmodify review
root@servername at /SNAP/probkup =>vgmodify -v -r -e 31999 -n -a -E vg_snap_probkup
Volume Group configuration for /dev/vg_snap_probkup has been saved in /etc/lvmconf/vg_snap_probkup.conf
Current Volume Group settings:
Max LV 255
Max PV 16
Max PE per PV 25599
PE Size (Mbytes) 16
VGRA Size (Kbytes) 3376
The current and new Volume Group parameters differ.
"/dev/rdisk/disk649" new configuration requires PEs are renumbered lower
An update to the Volume Group IS required
New Volume Group settings:
Max LV 255
Max PV 16
Max PE per PV 31999
PE Size (Mbytes) 16
VGRA Size (Kbytes) 4192
Review complete. Volume group not modified
root@servername at /SNAP/probkup =>vgmodify -v -r -a -E vg_snap_probkup
Volume Group configuration for /dev/vg_snap_probkup has been saved in /etc/lvmconf/vg_snap_probkup.conf
/dev/rdisk/disk649 Warning: Max_PE_per_PV for the volume group (25599) too small for this PV (31999).
Using only 25599 PEs from this physical volume.
An update to the Volume Group is NOT required
Review complete. Volume group not modified
Also attached is top of pvdisplay
--- Physical volumes ---
PV Name /dev/disk/disk649
VG Name /dev/vg_snap_probkup
PV Status available
Allocatable yes
VGDA 2
Cur LV 1
PE Size (Mbytes) 16
Total PE 25599
Free PE 4
Allocated PE 25595
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On
Proactive Polling On
--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg_snap_probkup/lvol1 25595 25595
--- Physical extents ---
PE Status LV LE
00000 free 00000
00001 current /dev/vg_snap_probkup/lvol1 00001
00002 current /dev/vg_snap_probkup/lvol1 00002
00003 current /dev/vg_snap_probkup/lvol1 00003
00004 current /dev/vg_snap_probkup/lvol1 00004
00005 current /dev/vg_snap_probkup/lvol1 00005
.
.
.
I'm confused.
How can I update the MAX_PE_PER_PV parameter to vgmodify the VG to use the full 500GB?
Also, do I need to lvextend afterwards?
Regards
Tariq
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2011 03:47 AM
10-17-2011 03:47 AM
Re: Cannot vgmodify VG after pvmove-ing extent zero
http://h30499.www3.hp.com/t5/LVM-and-VxVM/vgextend-Warning-Max-PE-per-PV/m-p/5085479
Search is a very useful tool in this forum.