AIX 0516-404 allocp: This system cannot fulfill the allocation

emre@sysaix:/ # chfs -a size=+1G /dizin
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.

The Upper Bound is 1 and your data is spread on one disk only:

 
emre@sysaix:/ # lslv dizinlv
LOGICAL VOLUME:     dizinlv               VOLUME GROUP:   vg10
LV IDENTIFIER:      00c2894e00004c000000010674bd4833.36 PERMISSION:     read/write
VG STATE:           active/complete        LV STATE:       opened/syncd
TYPE:               jfs2                   WRITE VERIFY:   off
MAX LPs:            512                    PP SIZE:        128 megabyte(s)
COPIES:             1                      SCHED POLICY:   parallel
LPs:                16                     PPs:            16
STALE PPs:          0                      BB POLICY:      relocatable
INTER-POLICY:       minimum                RELOCATABLE:    yes
INTRA-POLICY:       middle                 UPPER BOUND:    1
MOUNT POINT:        /dizin LABEL:          dizin
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes (superstrict)
Serialize IO ?:     NO
DEVICESUBTYPE : DS_LVZ

sysaix@root:/ # lslv -l dizinlv
10_lv069:/locate/database35
PV                COPIES        IN BAND       DISTRIBUTION
hdisk1          016:000:000   6%            002:131:102:562:009

In this situation, you cannot increase the LV if the targeted size will spread on more disks than the “UPPER BOUND” value. So you have to change it with the chlv command:

emre@sysaix:/ # chlv -u 1024 dizinlv

emre@sysaix:/ # lslv dizinlv
LOGICAL VOLUME:     dizinlv               VOLUME GROUP:   vg10
LV IDENTIFIER:      00c2894e00004c000000010674bd4833.36 PERMISSION:     read/write
VG STATE:           active/complete        LV STATE:       opened/syncd
TYPE:               jfs2                   WRITE VERIFY:   off
MAX LPs:            512                    PP SIZE:        128 megabyte(s)
COPIES:             1                      SCHED POLICY:   parallel
LPs:                178                    PPs:            178
STALE PPs:          0                      BB POLICY:      relocatable
INTER-POLICY:       minimum                RELOCATABLE:    yes
INTRA-POLICY:       middle                 UPPER BOUND:    1024
MOUNT POINT:        /dizin LABEL:          /dizin
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes (superstrict)
Serialize IO ?:     NO
DEVICESUBTYPE : DS_LVZ

SUPSID01@root:/ # chfs -a size=+7G /dizin
SUPSID01@root:/ # df -g /dizin
Filesystem    GB blocks      Free %Used    Iused %Iused Mounted on
/dev/dizinlv     31.25     31.24    1%        4     1% /dizin
 
0 (0)
Article Rating (No Votes)
Rate this article
Attachments
There are no attachments for this article.
Comments
There are no comments for this article. Be the first to post a comment.
Full Name
Email Address
Security Code Security Code
Related Articles RSS Feed
Replacing a failed disk (rootvg)
Viewed 3195 times since Mon, May 21, 2018
Configuration of AIX Fast Connect and SMBFS
Viewed 8781 times since Mon, Jun 18, 2018
This document discusses a new feature implemented for JFS2 filesystems to prevent simultaneous mounting.
Viewed 3009 times since Sat, Jun 1, 2019
Unlock User ID in IBM AIX
Viewed 15627 times since Mon, May 28, 2018
Processes and Devices—It’s All About the Children
Viewed 2416 times since Wed, May 30, 2018
Topics: PowerHA / HACMP, Storage Adding a new volume group to an active PowerHA resource group
Viewed 2829 times since Mon, Jun 3, 2019
Many Choices for AIX File Integrity
Viewed 2870 times since Wed, May 30, 2018
Convert to Scalable Volume Groups
Viewed 4279 times since Wed, May 30, 2018
Tunneling With SSH to Your Destination
Viewed 4586 times since Wed, May 30, 2018
Changing Ethernet Media Speed for AIX
Viewed 3598 times since Tue, Apr 16, 2019