IT14919: RETRIEVAL OPERATIONS FROM A CONTAINER STORAGE POOL MAY ERRONEOUSLY FAIL DUE TO ANR2818E ERROR

7.1.5.200-TIV-TSMSRV-AIX
7.1.5.200-TIV-TSMSRV-HP-UX
7.1.5.200-TIV-TSMSRV-Linuxppc64
7.1.5.200-TIV-TSMSRV-Linuxs390x
7.1.5.200-TIV-TSMSRV-Linuxx86_64
7.1.5.200-TIV-TSMSRV-SolarisSPARC
7.1.5.200-TIV-TSMSRV-WIN
7.1.6.000-TIV-TSMSRV-AIX
7.1.6.000-TIV-TSMSRV-HP-UX
7.1.6.000-TIV-TSMSRV-Linuxx86_64
7.1.6.000-TIV-TSMSRV-SolarisSPARC
7.1.6.000-TIV-TSMSRV-WIN
7.1.6.000-TIV-TSMSRV-Linuxppc64
7.1.6.000-TIV-TSMSRV-Linuxs390x
CNF3LML.ova
IBM Spectrum Protect Server V7.1.5.X interim fix downloads
IBM Spectrum Protect Server V7.1 Fix Pack 6 (7.1.6.000) Downloads

APAR status

• Closed as program error.

Error description

• A timing problem exists where an attempt to retrieve data from a
  container storage pool may fail if the retrieval operation is
  performed shortly after the data has been backed up, archived,
  replicated or protected.  Affected retrieval operations include
  PROTECT STGPOOL, REPLICATE NODE, AUDIT CONTAINER, and client
  retrievals.  The failure occurs because the retrieval operation
  attempts to access data that has not yet been flushed to media.
  The following error is generated in the activity log when this
  condition occurs:
  
     ANR2818E A consistency check failed on container
     /tsm/container/10/0000000000009999.dcf with error 4800.
  
  (Note: error 4800 can also be error 4801, error 4802 or error
  4803)
  
  Corresponding chunk header errors are also recorded in the
  dsmffdc.log file:
  
     [ FFDC GENERAL_SERVER_ERROR ]: (sdutil.c:4462) Chunk Header
     Invalid Signature chunkId: 5702387903525131283 Container:
     /tsm/container/10/0000000000009999.dcf Offset: 36929536
  
  After the ANR2818E error has occurred, a subsequent PROTECT
  STGPOOL operation will identify one or more damaged extents on
  the affected container:
  
     ANR4847W PROTECT STGPOOL detected an extent with ID
     5702387903525131283 on container
     /tsm/container/10/0000000000009999.dcf that is marked damaged
  
  Because the initial ANR2818E error occurred as the result of a
  timing problem, performing an audit of the affected container
  after the data has been successfully flushed to media will
  result in the extent(s) previously marked as damaged becoming
  undamaged:
  
     ANR2017I Administrator ADMIN issued command: AUDIT CONTAINER
     /tsm/container/10/0000000000009999.dcf
     ANR4886I Audit Container (Scan) process started for container
     /tsm/container/10/0000000000009999.dcf (process ID 165).
     ANR4891I AUDIT CONTAINER process 165 ended for the
     /tsm/container/10/0000000000009999.dcf container: 1728 data
     extents inspected, 0 data extents marked as damaged, 1 data
     extents previously marked as damaged reset to undamaged, 0
     data extents marked as orphaned, and 0 data extents
     previously marked as orphaned reset to unorphaned.
  
  In the event of a server crash prior to the data being
  successfully flushed to media, then the above ANR2818E error
  message may not be seen, but damaged extents may be detected on
  one or more containers in the storage pool. In this situation,
  the affected extents are damaged and cannot be resolved via the
  AUDIT CONTAINER process.
  
  Versions Affected:
  IBM Spectrum Protect server versions 7.1.3 and higher
  
  Initial Impact:
  Medium
  
  Additional Keywords:
  directory container chunk header extent flush timing
  

Local fix

• If the ANR2818E error is seen, quiesce all backup, archive,
  replication, and protect operations to the storage pool, wait
  for all of these sessions to end, and then perform an AUDIT
  CONTAINER on the affected container(s).
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users of container storage *
  * pools.                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is projected *
  * to be fixed in level 7.1.5.200 and 7.1.6. Note that this is  *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• The problem was fixed.
  
  Affected platforms: AIX, Linux, Windows, and Solaris.
  

Temporary fix

Comments

APAR Information

• 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