IC66609: TIVOLI STORAGE MANAGER CLIENT CRASH DURING INCREMENTAL BACKUP WITH SNAPDIFF OPTION WHEN EXCLUDED FILES ARE PROCESSED.

IBM Tivoli Storage Manager (TSM) Client 6.2.2 Downloads and READMEs

APAR status

• Closed as program error.

Error description

• A Tivoli Storage Manager V6.1 client may crash when using the
  -snapdiff option with the incremental backup.The crash occurs
  when the incremental backup processes a file excluded for
  backup. For example :
  
  1. In dsm.sys specifify the option "EXCLUDE filespec".
     For example:
     EXCLUDE /.../myfile
  2. Perform incremental backup with snapdiff.
  3. Create a new directory on the NAS/N-Series file server
     volume and create in this directory the file that should be
     excluded. For example:
       /my_netapp/myfile
  4. Start incremental backup with snapdiff.
  
  Under these circumstances, the client crashes. For example :
  
  # dsmc inc -snapdiff /my_netapp
  ...
  Incremental by snapshot difference of volume '/my_netapp'
  Directory-->               8,192 /my_netapp/ [Sent]
  ...
  ANS1898I ***** Processed    14,000 files *****
  ...
  Normal File-->               925 /my_netapp/path/filename [Sent]
  The assert subroutine failed: mgmtClass != NULL_MGMTCLASS,
  file cubackup.cpp, line 1373
  
  Fatal error: got signal  6
  IOT/Abort trap(coredump)
  
  Customer/L2 Diagnostics:
  In the case of a client running on AIX 5.3, the call stack of
  the core file produced by the crash shows :
  
  abort() at 0x900000000088260
  psunxthr.psAbort__Fv() at 0x10001ec98
  psunxthr.psTrapHandler__FiT1P12__sigcontext() at 0x10001ec0c
  pthread_kill(??, ??) at 0x90000000047789c
  _p_raise(??) at 0x9000000004772b0
  raise.raise(??) at 0x90000000005cbf8
  abort() at 0x90000000008822c
  __assert_c99(??, ??, ??, ??) at 0x900000000093fa0
  cubackup.cuBackInsEnh__FP6Sess_oP10fileSpec_tUcUiT4PcPUcT4UlT...
  senddata.sdSendObj__FP6Sess_oP8TxnBlockPFiP8TxnBlockPv_iPvP12...
  txncon.sendIt__FP17txnPrivConsumer_tP8TxnBlock() at 0x100272dd8
  txncon.PFtxnListLoop__FP19txnConsumerObject_ti() at 0x100272064
  txncon.PrivFlush2__FP19txnConsumerObject_t() at 0x100270d68
  txncon.PrivFlush__FP19txnConsumerObject_t() at 0x10026cd74
  txncon.tlSend__FP19txnConsumerObject_tP9txnSpec_tT2() at 0x10...
  bacontrl.HandleQueue__14DccTxnConsumerFv() at 0x100284f74
  bacontrl.Run__14DccTxnConsumerFPv() at 0x100284930
  bacontrl.DoThread__14DccTxnConsumerFPv() at 0x100285f2c
  bacontrl.callDoCThread2__FPv() at 0x100283c5c
  thrdmgr.startThread2__FP11Threadstart() at 0x100120f40
  thrdmgr.startThread__FP11Threadstart() at 0x100120e70
  
  TSM Versions Affected:
  TSM client V6.1 on all platforms.
  
  Additional Keywords:
  abend cored dump snap diff differential zz61
  

Local fix

• One of the following 3 methods may be used :
  
  1. Do not exclude files when running incremental backup with the
     -snapdiff option.
  2. If files must be excluded, use the exclude.dir option instead
     of the exclude option.
  3. If files must be excluded and the exclude.dir option is not
     appropriate, use the "TESTFLAG SNAPDIFFINCR" option in the
     client dsm.opt file.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Backup-archive client versions 6.1 and 6.2   *
  *                 running on IBM AIX and Microsoft Windows     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 6.1.4 and 6.2.2. Note that this    *
  *                 is subject to change at the discretion of    *
  *                 IBM.                                         *
  ****************************************************************
  *
  

Problem conclusion

• The problem has been fixed so the problem does not occur any
  more.
  

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:

Modules/Macros

• DSMC
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R61A PSY

     UP

• R61D PSY

     UP

• R61F PSY

     UP

• R61W PSY

     UP