IC69900: UNDER RARE CIRCUMSTANCES THE SERVER MAY HANG DURING DATA MOVEMENT PROCESSES

APAR status

• Closed as program error.

Error description

• Under rare circumstances the server may hang during data
  movement processes. This
  can include reclamation and the the backup stgpool operation but
  does not include others like export and generate backupset.
  The timing window is exposed when the server is attempting to
  process data that has been stored in a
  format other than NATIVE. For instance, a non-block storage pool
  can be susceptible to the hang
  situation. The process(es) can get into hang situation when an
  attempt is made to switch from an
  optimized copy to a non-optimized copy due to the data format.
  
  A SHOW THREADS can be issued to verify the hang condition as the
  reclamation process will show the
  following thread states:
  
  Thread 245, Parent 244: AfRclmVolumeThread, Storage 782337,
  AllocCnt 1569 HighWaterAmt 852837
   tid=26f5, ptid=25f4, det=1, zomb=0, join=0, result=0, sess=0
    Awaiting cond sessP->aux_1IdleCond (0x112491840), using mutex
  sessP->mutex (0x1134a9a38), at
  sstrans.c(11345)
    Stack trace:
      0x09000000005c0c10 _cond_wait_global
      0x09000000005c179c _cond_wait
      0x09000000005c248c pthread_cond_wait
      0x0000000100007eb4 pkWaitConditionTracked
      0x000000010071f9f4 WaitSourceIdle
      0x00000001007180a8 OptimizedCopyNC
      0x0000000100716d14 ssCopy
      0x0000000100866750 RelocateBitfile
      0x00000001008634b0 MoveBatch
      0x000000010085b3b8 MoveVolume
      0x000000010085a238 AfMoveVolume
      0x000000010096d288 AfRclmOnsiteVols
      0x000000010096b088 AfRclmVolumeThread
      0x0000000100009d68 StartThread
  
  Thread 246, Parent 245: SsSWThread, Storage 142395, AllocCnt 709
  HighWaterAmt 226848
   tid=24f6, ptid=26f5, det=1, zomb=0, join=0, result=0, sess=0
    Awaiting cond sinkCtlP->snkBeginCond (0x112491450), using
  mutex sessP->mutex (0x1134a9a38), at
  ssswtr.c(1688)
    Stack trace:
      0x09000000005c0c10 _cond_wait_global
      0x09000000005c179c _cond_wait
      0x09000000005c248c pthread_cond_wait
      0x0000000100007eb4 pkWaitConditionTracked
      0x0000000100619444 SsSWThread
      0x0000000100009d68 StartThread
  
  
  Thread 248, Parent 245: SsAuxSrcThread, Storage 80365, AllocCnt
  1153 HighWaterAmt 168207
   tid=27f8, ptid=26f5, det=1, zomb=0, join=0, result=0, sess=0
    Awaiting cond sessP->mediaSentCond (0x11248e200), using mutex
  sessP->mutex (0x1134a9a38), at
  sstrans.c(5653)
    Stack trace:
      0x09000000005c0c10 _cond_wait_global
      0x09000000005c179c _cond_wait
      0x09000000005c248c pthread_cond_wait
      0x0000000100007eb4 pkWaitConditionTracked
      0x0000000100721ea4 SsSendMediaMount
      0x00000001003883ec AsOpenSeg
      0x0000000100722e44 DoOpenSeg
      0x00000001007209f4 AuxAsSource
      0x0000000100720498 SsAuxSrcThread
      0x0000000100009d68 StartThread
  
  
  NOTE: If the platform does not support the callstack display for
  SHOW THREADS, an OS level command
  may be available such as PSTACK (linux and Solaris)
  
  Initial Impact:
  Medium
  .
  Tivoli Storage Manager Versions Affected:
  Tivoli Storage Manager Server version 6.2
  .
  Additional Keywords:
  TSM zz62 nonblock hang hung native volumes
  

Local fix

• Add DISABLEOPTIMIZEDCOPY to the dsmserv.opt file
  
  and stop and restart tsm server process/service.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All 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 6.2.1.2 and 6.2.2 .                *
  *                 Note that this is subject to change at the   *
  *                 discretion of IBM.                           *
  ****************************************************************
  See ERROR DESCRIPTION.
  

Problem conclusion

• The described problem has been resolved.
  

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

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP