Error Message

The issue is happening in specific circumstances that the size of the disk media objects and potentially other parameters would determine whether it occurs.

The problem was initially detected on Volume Manager 6.1.1.400, the issue could reside with earlier releases.

example showing mix-ed arrays allocation across different  plexes

incorrect allocation:

v  vol          -            ENABLED  ACTIVE   3550404608 ROUND   -        gen

pl vol-01       vol          ENABLED  ACTIVE   3550404608 CONCAT  -        RW

sd b1-01        vol-01       b1       0        2147419600 0       emc_clariion1_5 ENA

sd c1-01        vol-01       c1       0        1195264064 2147419600 emc_clariion1_6 ENA

sd d0-01        vol-01       d0       0        207720944 3342683664 emc_clariion0_153 ENA

pl vol-02       vol          ENABLED  ACTIVE   3550404608 CONCAT  -        RW

sd b0-01        vol-02       b0       0        2147419600 0       emc_clariion0_151 ENA

sd c0-01        vol-02       c0       0        1195264064 2147419600 emc_clariion0_152 ENA

sd d1-01        vol-02       d1       0        207720944 3342683664 emc_clariion1_7 ENA

Correct plex allocation:

v  vol          -            ENABLED  ACTIVE   3550404608 ROUND   -        gen

pl vol-01       vol          ENABLED  ACTIVE   3550404608 CONCAT  -        RW

sd b1-01        vol-01       b1       0        2147419600 0       emc_clariion1_5 ENA

sd c1-01        vol-01       c1       0        1195264064 2147419600 emc_clariion1_6 ENA

sd d1-01        vol-02       d1       0        207720944 3342683664 emc_clariion1_7 ENA

pl vol-02       vol          ENABLED  ACTIVE   3550404608 CONCAT  -        RW

sd b0-01        vol-02       b0       0        2147419600 0       emc_clariion0_151 ENA

sd c0-01        vol-02       c0       0        1195264064 2147419600 emc_clariion0_152 ENA

sd d0-01        vol-01       d0       0        207720944 3342683664 emc_clariion0_153 ENA

This problem was initially detected on Volume Manager 6.1.1.400, the issue could potentially occur on previous versions as well as all current version up to and including 7.4.2 [latest release as of the time of print]

There is currently no fix and the bug is expected to be addressed eventually in future InfoScale releases.

In the interim the following workaround can be implemented:

Create a new sub-disk

# vxmake -g dg sd d0-01 d0,0,207720944

Associate the sub-disk to the corresponding plex:

# vxsd -g dg assoc vol-02 d0-01

Create the second sub-disk:

# vxmake -g dg sd d1-01 d1,0,207720944

Associate the subdisk to the corresponding plex:

# vxsd -g dg assoc vol-01 d1-01

Note: Repeat as per the number of plex [mirrors]  that you have created for the volume

Update the size of the volume to the new size (current size + created SD size)

 # vxvol -g dg set len=$((3340763136+207720944)) 

Please note, the offset and length will need to be replaced 

Use vxresize to increase the mounted filesystem 

# vxresize -g dg vol 3550404608