0516-404 allocp: This system cannot fulfill the allocation

Issue:  volume group mirroring is giving error.

Error :

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.  
0516-1517 mklvcopy: Failed to create a valid partition allocation.
0516-842 mklvcopy: Unable to make logical partition copies for logical volume.
0516-1199 mirrorvg: Failed to create logical partition copies for logical  volume volume group.
0516-1200 mirrorvg: Failed to mirror the volume group.

In such cases, UPPER BOUND of lv`s has to be considered.

- Find out using lslv lvname, the UPPER BOUND value should be atleast equal to the number of disks, if not it gives the above error.
 
#  lslv testlv
LOGICAL VOLUME:    testlv                 VOLUME GROUP:   testvg
LV IDENTIFIER:      00c502df00004c00000001233479719d.6    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:                296                         PPs:            296
STALE PPs:          0                       BB POLICY:      relocatable
INTER-POLICY:       minimum                RELOCATABLE:    yes
INTRA-POLICY:       middle                 UPPER BOUND:   128 --> Min = Equal to no.of disks.
                                                                                   --> Max = Depends on VG Type
MOUNT POINT:        /testfs             LABEL:          /testfs
DEVICE UID:         0                      DEVICE GID:     0
DEVICE PERMISSIONS: 432
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?:     NO
INFINITE RETRY:     no



Also when we add disks to the VG this upper bound value should be checked once, for all the lv`s in the volume group and make sure it is atleast equal to the number of disks in the volume group and max value depends on the type of VG. i.e it will be the max disks that can be part of a vg.

To change the UPPER BOUND value for an LV :

chlv -u (value to be changed)  lvname

In simple words, only if the lv is allowed to have upper bound atleast equal to number of disks, then all the lv based operating system commands will work with out any issues, be it lvcopy, vg mirror etc..,