IBM Support

IT24043: AFTER A SERVER CRASH, A CONTAINER IN THE CACHE USED FOR A CLOUD POOL CAN BECOME UNAVAILABLE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • After an IBM Spectrum Protect server crash it is possible that
    a container in the cache used for a S3 or Azure cloud pool can
    become unavailable.
    (Azure is supported from version 8.1.3)
    After server restart, when attempting to use the container
    again, you would see the following messages:
    ANR0204I The container state for
    /fs/cache/9d/0000000000009d2d.dcf is updated from READONLY to
    UNAVAILABLE. (PROCESS: 1)
    ANR3660E An unexpected error occured while opening or writing to
    the container. Container /fs/cache/9d/0000000000009d2d.dcf in
    stgpool CLOUDPOOL has
    been marked as UNAVAILABLE and should be audited to validate
    accessibility and content. (PROCESS: 1)
    ANR2088E An I/O error ocurred while reading container
    /fs/cache/9d/0000000000009d2d.dcf in storage pool CLOUDPOOL.
    (PROCESS: 1)
    The container will not be present in the directory path.
    This issue is very rare, and for it to occur, connections would
    need to be lost to DB2 before the rest of IBM Spectrum Protect
    server crashed.
    Examples are when Linux out-of-memory killer (oom-killer) kills
    off processes due to shortage of memory and swap space, and AIX
    PGSP_KILLs occur when paging space is exhausted.
    Initial Impact: Medium
    IBM Spectrum Protect versions affected:
    Server 7.1.x and 8.1.x and higher on all supported platforms
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IBM Spectrum Protect server users of S3 and Azure type   *
    * cloud storage pools.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See error description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in levels 8.1.5 and 7.1.9. Note that   *
    * this is subject to change at the discretion of IBM.          *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IT24043

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    81L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-12

  • Closed date

    2018-03-02

  • Last modified date

    2018-03-02

  • 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: 81L

Reference #: IT24043

Modified date: 02 March 2018