IBM Support

IV56029: MIRRORVG MAY NOT ALLOCATE PPS IN THE ORDER OF SPECIFIED PVS APPLIES TO AIX 7100-03

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When Physical Volumes are specified for new copies of
    Logical Volume in the mirrorvg command, allocation of
    Physical Partitions on Physical Volumes is not in the
    order of Physical Volumes specified in the command line.
    
    A snippet to explain the above:
    
    mkvg -y wu32748vg -f hdisk1 hdisk2 hdisk3 hdisk4 hdisk5
    hdisk6
    mklv -y wu32748lv -e x -s s wu32748vg 3 hdisk1 hdisk2
    hdisk3
    mirrorvg -s -m -c 2 wu32748vg hdisk4 hdisk5 hdisk6
    lslv -m wu32748lv
    
    $ lslv -m wu32748lv
    wu32748lv:N/A
    LP    PP1  PV1               PP2  PV2               PP3
    PV3
    0001  0161 hdisk1            0161 hdisk5
    0002  0161 hdisk2            0161 hdisk6
    0003  0161 hdisk3            0161 hdisk4
    

Local fix

  • Run mirrorvg without -m.
    
    mkvg -y wu32748vg -f hdisk1 hdisk2 hdisk3 hdisk4 hdisk5
    hdisk6
    mklv -y wu32748lv -e x -s s wu32748vg 3 hdisk1 hdisk2
    hdisk3
    mirrorvg -s -c 2 wu32748vg hdisk4 hdisk5 hdisk6
    lslv -m wu32748lv
    
    $ lslv -m wu32748lv
    wu32748lv:N/A
    LP    PP1  PV1               PP2  PV2               PP3
    PV3
    0001  0161 hdisk1            0161 hdisk4
    0002  0161 hdisk2            0161 hdisk5
    0003  0161 hdisk3            0161 hdisk6
    

Problem summary

  • mirrorvg -m has some logic that can mix up the order of the
    disks that an LV is currently allocated on.  When this happens,
    the newly allocated copies of the LV will not use the PVs in
    the order they were listed on the command line.
    
    This happens when the LV is allocated on PVs in an order that
    is not the same as if those PVs are sorted by pvid.
    
    Note that there are sometimes when mirrorvg -m must rearrange
    disks when allocating new copies so that those new copies can
    be an exact map of the existing copies.  But in some cases,
    when all disks are the same size, mirrorvg is re-ordering
    disks when it doesn't need to.
    

Problem conclusion

  • Change mirrorvg -m logic to not re-order PVs in this case when
    it is not necessary, but just being done as an easy way to get
    unique pvids the LV is allocated on.
    

Temporary fix

Comments

  • 6100-07 - use AIX APAR IV58727
    6100-08 - use AIX APAR IV58655
    6100-09 - use AIX APAR IV58084
    6100-09 - use AIX APAR IV58084
    6100-09 - use AIX APAR IV58084
    7100-01 - use AIX APAR IV58239
    7100-02 - use AIX APAR IV58175
    7100-03 - use AIX APAR IV56029
    7100-04 - use AIX APAR IV58091
    

APAR Information

  • APAR number

    IV56029

  • Reported component name

    AIX V7.1

  • Reported component ID

    5765H4000

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Submitted date

    2014-02-27

  • Closed date

    2014-03-25

  • Last modified date

    2016-05-10

Fix information

  • Fixed component name

    AIX V7.1

  • Fixed component ID

    5765H4000

Applicable component levels

  • R710 PSY U859005

       UP14/05/22 I 1000

PTF to Fileset Mapping



Document information

More support for: AIX Enterprise Edition

Software version: 710

Operating system(s): AIX

Reference #: IV56029

Modified date: 10 May 2016