IC80690: BACKUP STGPOOL WITH MAXPROCESS GREATER THAN 1 MIGHT ENCOUNTER PROCESSING DELAYS OR POSSIBLY RESOURCE WAITER ABORTS.

APAR status

• Closed as program error.

Error description

• Backup Storage pool processes might get into wait conditions if
  more than one process is spawned and volumes contain spanned
  files. A file is considered spanned if it has storage segments
  on more than one volume. The symptom will be that at least one
  process will appear to not process a volume, or files, for long
  periods of time. if this period of time is greater than the
  RESOURCETimeout value, the process might fail with a ANR0538I
  message indicating a resource waiter has been aborted.
  NOTE: This will typically be encountered in a storage pool of
  devtype FILE.
  
  Customer/L2 Diagnostics:
  
  Actlog:
  ANR2017I Administrator xxx issued command: BACKUP STGPOOL xxx
  yyy maxpr=2
  ANR0984I Process 37 for BACKUP STORAGE POOL started in the
  BACKGROUND at 04:51:58 PM.
  ANR2110I BACKUP STGPOOL started as process 37.
  ANR1210I Backup of primary storage pool xxx to copy storage pool
  yyy started as process 37.
  ANR0984I Process 38 for BACKUP STORAGE POOL started in the
  BACKGROUND at 04:51:59 PM.
  ANR2110I BACKUP STGPOOL started as process 38.
  ANR1210I Backup of primary storage pool xxx to copy storage pool
  yyy started as process 38.
  ...
  ANR0538I A resource waiter has been aborted.
  ...
  ANR0986I Process 37 for BACKUP STORAGE POOL running in the
  BACKGROUND processed 810,368 items for a total of 28,778,040,810
  bytes with a completion state of FAILURE at 06:31:49 AM.
  ANR1893E Process 37 for BACKUP STORAGE POOL  completed with a
  completion state of FAILURE.
  ...
  ANR0986I Process 38 for BACKUP STORAGE POOL running in the
  BACKGROUND processed 2,560,281 items for a total of
  114,075,873,037 bytes with a completion state of FAILURE at
  07:00:12 AM.
  ANR1893E Process 38 for BACKUP STORAGE POOL  completed with a
  completion state of FAILURE.
  
  A Show Thread and Show Locks will have the child thread waiting
  for the same Backup STG process:
  Thread 51738, Parent 51735: AfBackupPoolThread, Storage
  21161658, AllocCnt 492929 HighWaterAmt 71660328
   tid=1393953088, ptid=1392900416, det=1, zomb=0, join=0,
  result=0, sess=0
    Awaiting cond waitP->waiting (0x0x2accf456e9c0), using mutex
  TMV->mutex (0x0x17077748), at tmlock.c(739)
  
  Thread 51737, Parent 51735: AfBackupPoolThread, Storage
  21265471, AllocCnt 730316 HighWaterAmt 21266096
   tid=1197103424, ptid=1392900416, det=1, zomb=0, join=0,
  result=0, sess=0
    Holding mutex txnP->mutex (0x0x1d470e88), acquired at
  tbcli.c(1027)
  
  LockDesc: Type=46001(bf aggregate (superbitfile) id),
  NameSpace=0, SummMode=xLock, Key='87625213'
    Holder: (bfaggrut.c:4782 Thread 51737) Tsn=0:5150692,
  Mode=xLock
    Waiter: (bfaggrut.c:4782 Thread 51738) Tsn=0:5141702,
  Mode=sLock
  
  Initial Impact: Low
  
  Additional Keywords: TSM more > maxpr stg
  

Local fix

• Run the Backup STGPool with maxpr=1.
  A longer term fix is to ensure that volume sizes in the storage
  pool match the average file size being stored in the given
  storage pool. This will help prevent massive amounts of volume
  spanning.
  

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.5 and 6.3.2.             *
  *                 Note that this is subject to change at       *
  *                 the discretion of IBM.                       *
  ****************************************************************
  *
  

Problem conclusion

• The described problem has been resolved.
  
  AFFECTED PLATFORMS:
  AIX, HP-UX, Solaris, Linux, 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

• 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

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP