IT36573: ANR9999D SDWRITECONTAINER(SDIO.C:1590) THREAD<XXXX>: IMPROPER SETUP FOR WRITING TO CONTAINER XXXXXXXXX (NIL) TRUE

APAR status

• Closed as program error.

Error description

• Starting with version 8.1.10.000 the IBM Spectrum Protect Server
  crashes with these symptoms during a directory container
  defragmentation:
  
  
  
  ANR4392I CONTAINER DEFRAGMENTATION started processing stgpool
  DEDUPCONTAINERPOOL. Containers are
  
  only using 91.90% of 14295.99 GB due to fragmentation.
  
  ANR0984I Process 14 for Move Container (Automatic) started in
  the BACKGROUND at 15:59:37.
  
  ANR0984I Process 15 for Move Container (Automatic) started in
  the BACKGROUND at 15:59:37.
  
  ANR0984I Process 16 for Move Container (Automatic) started in
  the BACKGROUND at 15:59:37.
  
  ANR0984I Process 17 for Move Container (Automatic) started in
  the BACKGROUND at 15:59:37.
  
  ANR0984I Process 18 for Move Container (Automatic) started in
  the BACKGROUND at 15:59:37.
  
  ANR9999D_1199904567 SdWriteContainer(sdio.c:1590) Thread<421>:
  Improper setup for writing to container 00000032BB178220 (nil)
  True
  
  ANR9999D Thread<421> issued message 9999 from:
  
  ANR9999D Thread<421>  7f849779672 OutDiagToCons()+b2
  
  ANR9999D Thread<421>  7f8497727d2 outDiagfExt()+122
  
  ANR9999D Thread<421>  7f8494a4cde SdWriteContainer()+45e
  
  ANR9999D Thread<421>  7f8494a58a8 SdWrite()+b58
  
  ANR9999D Thread<421>  7f849488b1d ProcessDefragData()+20d
  
  ANR9999D Thread<421>  7f849487355 ProcessStreamBuffer()+225
  
  ANR9999D Thread<421>  7f849485bea SdCntrStreamThread()+145a
  
  ANR9999D Thread<421>  7f848a6d253 startThread()+5b3
  
  ANR9999D Thread<421>  7f85ce4f4a0 o__realloc_base()+60
  
  ANR9999D Thread<421>  7f864b81652 BaseThreadInitThunk()+1a
  
  
  
  The stack from the Linux core will show:
  
  
  
  Program terminated with signal 11, Segmentation fault.
  
  #0  SdBuildContainerFreeList (txnId=<optimized out>,
  cntrP=0x7fad880483f0,
  
  #1  AssignContainer (getSufficientRange=False,
  descPP=0x7fad47127e00,
  
  #2 SdAcquireContainer (txnP=txnP@entry=0x7facf80955a0,
  dirP=<optimized out>,
  
  #3  SdAcquireAnyContainerEx (txnP=txnP@entry=0x7facf80955a0
  
  #4  SdWrite (txnP=0x7facf80955a0,
  chunkP=chunkP@entry=0x7facf80093e0,
  
  #5  ProcessDefragData (bufSize=0x7fad47127fe8,
  bufP=0x7fad47128020,
  
  
  
  
  
  
  
  
  
  Also it may crash as follow:
  
  
  
  Program terminated with signal 11, Segmentation fault.
  
  #0 in pthread_mutex_lock ()
  
  ================================================================
  =========
  
  #0 pthread_mutex_lock
  
  #1  pkAcquireMutexTracked
  
  #2 SdReleaseRange
  
  #3  SdWrite
  
  #4 ProcessDefragData
  
  #5  ProcessStreamBuffer
  
  #6 SdCntrStreamThread
  
  
  
  with the following ANR9999D
  
  
  
  ANR0984I Process 43 for Move Container (Automatic) started in
  the BACKGROUND at 11:54:20 AM. (PROCESS: 43)
  
  ANR9999D_0031136775 CheckSegment(sdcntr.c:8752) Thread<90925>:
  Inconsistent listSize 3 and head (nil), tailP (nil) in big
  linked list 0x7f77e81aa000. (PROCESS: 39)
  
  ANR9999D Thread<90925> issued message 9999 from: (PROCESS: 39)
  
  
  
  | MDVREGR 8.1.10-TIV_5698MSV |
  
  | MDVREGR 8.1.11-TIV_5698MSV |
  
  
  
  IBM Spectrum Protect Server version Affected: Spectrum Protect
  Servers 8.1.10.xxx and 8.1.11.xxx and above on all supported
  platforms
  
  
  
  
  
  Initial Impact: high
  
  
  
  Additional Keywords:   ANR9999D_0031136775 ANR4392I CONTAINER
  DEFRAGMENTATION TS005092387 SdWriteContainer improper setup
  abend crash
  

Local fix

• Auto defrag can be disabled by:
  setopt disableautodefrag yes
  and restart server
  
  
  Also, avoid using 'move container' command manually.
  

Problem summary

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

Problem conclusion

• This problem was fixed.
  

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