IC67947: DEADLOCK WHEN DELETE VOLUME HISTORY AND LABEL LIBRARY VOLUME PROCESSES RUN AT THE SAME TIME.

IBM Tivoli Storage Manager V6.1 Fix Pack 4 (6.1.4) Server Downloads

APAR status

• Closed as program error.

Error description

• Tivoli Storage Manager server may encounter a deadlock situation
  when delete volhistory and label libvol activity are
  running at the same time.
  Show output at the time of this problem reveals:
  From show resqueue - waiters for type=77778
  From show locks - waiting for lock type=77778
     LockDesc: Type=77778(unknown), NameSpace=7, SummMode=xLock,
               Key=''
        Holder: (icutil.c:1534 Thread 1160697) Tsn=0:159755170,
                Mode=xLock
        Waiter: (icutil.c:1534 Thread 1164644) Tsn=0:161228719,
                Mode=sLock
        Waiter: (icutil.c:1534 Thread 1076769) Tsn=0:161233294,
                Mode=sLock
  From show threads - using above thread information shows lock
                      holder thread (1160697) waiting on relabel
                      condition and label activity (thread
                      1164644) waiting on lock being held.
  Thread 1160697, Parent 1153314: SmAdminCommandThread, Storage
  173257, AllocCnt 162 HighWaterAmt
  208925
   tid=bbf9, ptid=bc22, det=0, zomb=0, join=1, result=0, sess=0
    Awaiting cond libP->relabelCond (0x110971dc0), using mutex
  libP->relabelMutex (0x111396dd8), at
  mmsscsi.c(2536)
    Stack trace:
      0x0900000000714d50 _cond_wait_global
      0x09000000007158dc _cond_wait
      0x09000000007165cc pthread_cond_wait
      0x0000000100007c74 pkWaitConditionTracked
      0x0000000100967c64 ScsiDeleteVolume
      0x0000000100335424 MmsDeleteVolume
      0x0000000100a8ce08 LtoDeleteVolume
      0x0000000100274364 pvrDelete
      0x0000000100314750 DeleteFromPvr
      0x0000000100312dbc icDeleteVolumeHistory
      0x0000000100ac3088 AdmDeleteVolumeHistory
      0x0000000100175ce0 AdmCommandLocal
      0x000000010017434c admCommand
      0x000000010078f3b4 SmAdminCommandThread
      0x0000000100009bb4 StartThread
  Thread 1164644, Parent 1160697: LabelThread, Storage 127697,
  AllocCnt 164 HighWaterAmt 177757
   tid=3664, ptid=bbf9, det=1, zomb=0, join=0, result=0, sess=0
    Awaiting cond waitP->waiting (0x1109a2dc0), using mutex
  TMV->mutex (0x110a0c6b8), at tmlock.c(721)
    Stack trace:
      0x0900000000714d50 _cond_wait_global
      0x09000000007158dc _cond_wait
      0x09000000007165cc pthread_cond_wait
      0x0000000100007c74 pkWaitConditionTracked
      0x00000001000c3fc4 tmLockTracked
      0x0000000100325174 LockVolumeTypeId
      0x0000000100323ccc LockVolumeType
      0x0000000100323764 IcLockVolumeHistory
      0x000000010030ee28 icIsVolumeUsed
      0x000000010006145c MmsVolumeHistoryExists
      0x000000010006116c MmsSkipVolume
      0x000000010096e9f4 AutoLabelVolume
      0x000000010096e36c ScsiLabelVolume
      0x0000000100338148 MmsLtsLabelVolume@AF75_53
      0x0000000100066d28 LabelThread
      0x0000000100009bb4 StartThread
  Tivoli Storage Manager Versions Affected: 5.4, 5.5, 6.1,6.2
  Initial Impact: Medium
  

Local fix

• To not run delete volume history and label libvol commands
  at the same time.
  

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 5.5.5, 6.1.4, and 6.2.2. Note      *
  *                 that this is subject to change at the        *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Sun Solaris, Linux,
  z/OS, and Windows.
  

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

• R55A PSY

     UP

• R55H PSY

     UP

• R55L PSY

     UP

• R55S PSY

     UP

• R55W PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP