IBM Support

IT19338: MOVE CONTAINER FAILS WITH ANR0203E INSUFFICIENT SPACE FOR NON DEDUP CONTAINER

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Error Description:
    
    Performing a MOVE CONTAINER command on a directory to another
    directory which has available space to accommodate the
    containers, may fail with :
    
    ANR0203E MOVE CONTAINER process nnn terminated for
    /Directory_being_moved_from/01/0000000000000110.ncf -
    insufficient space in directory /Directory_being_moved_to
    
    
    Customer/L2 Diagnostics (If Applicable)
    
    Whilst the original directory may have a mixture of dedup and
    non dedup container files, the failure will be encountered for a
    non dedup container. Eg  :
    
    Container
    ----------------------------------------------------
     /Directory_being_moved_from/01/0000000000000110.ncf
    
    Storage Pool Name
    -----------------
     MYSDPOOL
    
    Container Type
    --------------
     Non Dedup
    
    State
    --------
     Available
    
    Free Space(MB)
    --------------
          0
    
    Maximum Size(MB)
    ----------------
      5 120
    
    
    On this occasion, there is only a single 5GB non dedup container
    file within this location.
    
    The directory location to move the container into will show it
    has space available. From a "show sddirectory" output :
    
    SD Storage Pool Directory /Directory_being_moved_to (3):
       Storage Pool:            MYSDPOOL (4)
       Absolute Directory Name: /Directory_being_moved_to
       File System Name:        /Directory_being_moved_to
       Access:                  READWRITE
    
       Total Bytes:             9663676416000
       Available Bytes:         7930928799744
       Stored Dedup Bytes:      1484956409895
       Stored NonDedup Bytes:   146581564581
       Last Allocation Time:    2017-02-09 04:32:42
    
    
    Obtaining a server trace using classes "sd" will show messages
    similar to the following :
    
    15:57:45.733 [353457][sdcntr.c][3219][SdOpenContainer]:Enter for
    container /Directory_being_moved_to/06/0000000000000686.ncf
    (1670), mode 4
    15:57:45.777 [353457][sdcntr.c][3435][SdOpenContainer]:Allocated
    container/Directory_being_moved_to/06/0000000000000686.ncf
    (1670) for 5368709120 bytes
    
    At this point, the correct number of bytes have been allocated
    for the container prior to the move.
    ..
    15:57:45.777 [353457][sddefrag.c][1603][SdMoveContainer]:Moving
    container  /Directory_being_moved_from/01/0000000000000110.ncf
    to target container
    /Directory_being_moved_to/06/0000000000000686.ncf with size of
    5368709120.
    ..
    
    "Invalid SD Range" is seen after the move is started :
    
    15:58:38.484
    [353457][sddefrag.c][1915][SdMoveContainer]:Adjusting offset of
    chunk -2628243587177084876 from 5368707586 to 5368708178
    15:58:38.484 [353457][sdio.c][1359][SdWriteContainer]:Invalid SD
    Range (offset 5368708178, length 942): container offset
    5368708178, length 1021.
    15:58:38.484 [353457][sdio.c][1428][SdWriteContainer]:Exit:
    rc=2370, cntrId 1670
    15:58:38.484 [353457][sddefrag.c][1935][SdMoveContainer]:Target
    container /Directory_being_moved_to/06/0000000000000686.ncf
    failed with out of space with file size 5368709120 and file
    position 5368708178.
    15:58:38.484 [353457][sddefrag.c][1940][PutConsoleMsg]:ANR0203E
    MOVE CONTAINER process 1140 terminated for
    /Directory_being_moved_from/01/0000000000000110.ncf -
    insufficient space in directory /Directory_being_moved_to
    
    The problem shows that there is an issue where non dedup
    containers are incorrectly being block aligned.
    
    When the container is first written, it's block aligned in 4k
    blocks, which leaves "gaps" in the container. During ingest of
    data, these "gaps" are incorrectly identified as available space
    for writing data to and are filled with more chunks. When a move
    of the container is performed, the allocation of space correctly
    matches the container's file size, but then chunks are aligned
    in 4k blocks again, which would take more space than was
    allocated, leading to the insufficient space error.
    
    IBM Spectrum Protect versions Affected:
    IBM Spectrum Protect versions 7.1.3 and higher on all platforms
    
    Initial Impact: Low|Medium|High
    Medium
    
    Additional Keywords:
    TSM, Spectrum Protect, move, space, nondedup, non-dedup
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IBM Spectrum Protect and Tivoli Storage Manager server   *
    * users.                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See error description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in levels 7.1.7.200, 7.1.8, and 8.1.1. *
    * Note that this is subject to change at the discretion of     *
    * IBM.                                                         *
    ****************************************************************
    

Problem conclusion

  • This problem was fixed.
    Affected platforms for reported release:  AIX, Solaris, Linux,
    and Windows.
    Platforms fixed:  AIX, Linux, Solaris, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT19338

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-21

  • Closed date

    2017-04-24

  • Last modified date

    2017-04-24

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    TSM SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R71A PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP

  • R81A PSY

       UP

  • R81L PSY

       UP

  • R81W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 7.1.3

Reference #: IT19338

Modified date: 24 April 2017