IC77971: SERVER CAN CRASH IN ASCANCELSDMEDIAWAITS

IBM Tivoli Storage Manager (TSM) server V6.2.3.x interim fix downloads

APAR status

• Closed as program error.

Error description

• Server crash can happen when a process has acquired a mount
  point and is in media wait.
  This can only occur with processes that use non storage pool
  volumes such as DBBACKUP, BACKUPSETS and EXPORT.
  This only occurs in a situation where the process is
  de-allocating the mount point due to a volume acquisition
  failure.
  
  It can also occur when reclamation fails due to not enough file
  space and process
  repeats over and over.
  
  ie
  ANR4930I Reclamation process 65678 started for
  primary storage pool POOLA automatically,
  threshold=80, duration=None.
  ANR4932I Reclamation process 65678 ended for
  storage pool POOLA. (PROCESS: 65678)
  ANR0985I Process 65678 for SPACE RECLAMATION
  running in the BACKGROUND completed with completion state
  SUCCESS
  ANR4936I Reclamation of storage pool
  POOLA has ended. Files reclaimed: 0,
  Bytes reclaimed: 0, Files reconstructed: 0, Unreadable
  files: 0.
  
  Stack on aix can look like:
  
   assd.asCancelSdMediaWaits(??, ??) at 0x1005e3758
  bfsd.bfCancelSdMediaWaits@AF17_10(??, ??, ??) at 0x1005df0f0
  icback.icCancelBackup(??, ??, ??) at 0x1005dbfbc
  process.procServerHalting() at 0x10048c8e0
  dbiinit.dbiHalt(??, ??, ??, ??) at 0x1004e62b4
  admstart.admStartServer(??, ??) at 0x1004db484
  dsmserv.main(??, ??) at 0x100000ee8
  
  
  
  Initial Impact:
  Medium
  .
  Tivoli Storage Manager Server Versions Affected:
  All versions and all platforms
  .
  Additional Keywords:
  TSM ZZ61 ZZ62 crash core space repeat
  

Local fix

• Ensure there is anough space to complete operations.
  

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 level 6.2.4.                        *
  *                 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

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP