28 3836 122753
30 3580 114561
32 3324 106369
35 3068 98177
38 2812 89985
...
255 252 8065
The table shows that without renumbering physical extents, a
max_pv
of 35 or lower permits
a
max_pe
sufficient to accommodate the increased physical volume size.
# vgmodify -v -t -n vg32
Volume Group configuration for /dev/vg32 has been saved in
/etc/lvmconf/vg32.conf
Current Volume Group settings:
Max LV 255
Max PV 16
Max PE per PV 1016
PE Size (Mbytes) 32
VGRA Size (Kbytes) 176
VGRA space (Kbytes) on all Physical Volumes:
PV current -n
/dev/rdisk/disk6 896 32768
/dev/rdisk/disk5 896 32768
Summary 896 32768
Volume Group optimized settings (PEs renumbered lower):
max_pv(-p) max_pe(-e) Disk size (Mb)
61 65535 2097152
62 65532 2097056
63 64252 2056096
...
251 16124 516000
252 16048 513568
255 15868 507808
The table shows that if physical extents are renumbered, all values of
max_pv
permit a
max_pe
large enough to accommodate the increased physical volume size.
For this example, select a
max_pv
of 10, which permits a
max_pe
value of 10748.
4.
Preview the changes by using the
-r
option to
vgmodify
as follows:
# vgmodify -p 10 -e 10748 -r vg32
Current Volume Group settings:
Max LV 255
Max PV 16
Max PE per PV 1016
PE Size (Mbytes) 32
VGRA Size (Kbytes) 176
The current and new Volume Group parameters differ.
"/dev/rdisk/disk6" size changed from 4194304 to 100000000kb
An update to the Volume Group IS required
New Volume Group settings:
Max LV 255
Max PV 10
Max PE per PV 10748
PE Size (Mbytes) 32
VGRA Size (Kbytes) 896
Review complete. Volume group not modified
5.
Deactivate the volume group as follows:
# vgchange -a n vg32
Volume group "vg32" has been successfully changed.
80
Administering LVM
