Troubleshooting
Problem
Attempt to increase logical volume in PowerVM Virtual I/O Server rootvg using extendlv command fails.
Symptom
$ extendlv lg_dumplv 3G
Some error messages may contain invalid information
for the Virtual I/O Server environment.
0516-404 allocp: This system cannot fulfill the allocation request.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The command
should be retried with different allocation characteristics.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The command
should be retried with different allocation characteristics.
Cause
The physical volume(s) in rootvg do not have enough space to increase the logical volume by the specified size.
Environment
PowerVM Virtual I/O Server version 3.1.X
Diagnosing The Problem
Verified the physical volumes (hdisk#s) in rootvg have enough space.
If the volume group is mirrored, both disk must have checked.
Resolving The Problem
In this example, we attempt to increase logical volume, lg_dumplv, by 3 GB.
1. Login to the Virtual I/O Server as padmin.
2. Determine if the logical volume is mirrored.
$ lslv lg_dumplv -field copies
COPIES: 1
COPIES: 1
1 = not mirrored
2 = mirrored
NOTE: If the volume group is mirrored, both mirrored disks must have enough space.
In this example, lg_dumplv is not mirrored, but if it was mirrored, each mirrored hdisk would need to have, at least, 3 GB of free space.
To list the physical volumes (hdisk#) where the logical volume resides on, run:
$ lslv -pv LVNAME
4. Determine how much free space there is in rootvg.
$ lsvg rootvg -field "free pps"
MAX LVs: 256 FREE PPs: 20 (2560 megabytes)
In this case, the error is valid since we tried to increase the logical volume by 3 GB, but there are only ~2.5 GB (2560 megabytes) free.
MAX LVs: 256 FREE PPs: 20 (2560 megabytes)
In this case, the error is valid since we tried to increase the logical volume by 3 GB, but there are only ~2.5 GB (2560 megabytes) free.
Solution
1. Add another physical volume to the volume group:
$ extendvg rootvg new_hdisk#
Note: If current rootvg physical volume is a SAN disk, it is not supported to resize the rootvg volume group as noted in chvg command:
| -chksize |
Examines all the disks in the volume group to determine whether they have increased in size. This option does not support resizing a volume group while it is activated in classic or enhanced concurrent mode. This option does not support resizing the rootvg volume group. |
Document Location
Worldwide
[{"Type":"SW","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"ARM Category":[{"code":"a8m0z0000001i2sAAA","label":"PowerVM VIOS-\u003ELVM"}],"ARM Case Number":"TS005690465","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0;3.1.1;3.1.2"}]
Was this topic helpful?
Document Information
Modified date:
20 May 2021
UID
ibm16454863