IT16403: DSMC CRASH WHEN DSMINSTR.LOG RENAME

Download Information: Version 8.1.0 IBM Spectrum Protectâ„¢ for Virtual Environments
IBM Spectrum Protect client 7.1.6.x interim fix downloads

APAR status

• Closed as program error.

Error description

• When the instrumentation dsminstr.log file is renamed due to
  reaching maximum size (default or specified by INSTRLOGMAX),
  the dsmc client crashes with the message.
  "*** glibc detected *** dsmc: double free or corruption
  (!prev): 0x0000000002c53cf0 ***".
  The dsminstr.log is renamed to dsminstr.log.bak but dsmc exits
  and no new dsminstr.log file is created (until the next dsmc
  invocation).
  Tivoli Storage Manager Versions Affected: 7.1.6 all platforms
  Customer/L2 Diagnostics:
  Collected on RHEL 6.7.  Other platforms will vary.
  *** glibc detected *** dsmc: double free or corruption (!prev):
  0x00000000020a7cf0 *** ======= Backtrace: =========
  /lib64/libc.so.6[0x324da75f3e] /lib64/libc.so.6[0x324da78dd0]
  /lib64/libc.so.6(fclose+0x14d)[0x324da6648d] dsmc[0x6e5128]
  dsmc[0x6e597a] dsmc[0x433471] dsmc[0x43441a]
  dsmc(__gxx_personality_v0+0x312)[0x430c2a]
  /lib64/libc.so.6(__libc_start_main+0xfd)[0x324da1ed1d]
  dsmc(__gxx_personality_v0+0x261)[0x430b79]
  

Local fix

• UNIX: set 'ENABLEINSTRUMENTATION No' in dsm.sys
  Windows: set 'ENABLEINSTRUMENTATION No' in dsm.opt
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of the following products:                             *
  * - Spectrum Protect backup-archive client version 7.1.6 on    *
  * all platforms                                                *
  * - Spectrum Protect for Virtual Environments component Data   *
  * Protection for VMware version 7.1.6 on Linux x86 and Windows *
  * x64                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is projected *
  * to be fixed in level 7.1.6.3. Note that this is subject to   *
  * change at the discretion of IBM.                             *
  ****************************************************************
  

Problem conclusion

• Nearly all client operations (including vm backups) might get
  core dumps with symptoms of corrupted memory if the
  instrumentation log processing was enabled (it is enabled, by
  default) and the instrumentation log file size exceeded the
  maximum size value set by the INSTRLOGMAX option (25 megabyte,
  by default).
  After the fix, the instrumentation log operations work fine.
  

Temporary fix

• A fix for this problem is currently targeted for Tivoli Storage
  Manager Client interim fix package version 7.1.6.3.
  
  Note 1: Until a Data Protection for VMware packaged fix of a
  fixing Tivoli Storage Manager Client level is available, Data
  Protection for VMware customers can install and use a fixed
  level of the the Tivoli Storage Manager Client in their
  environment.
  Note 2: The Tivoli Storage Manager (TSM) Client is a part of the
  Data Protection for VMware. In Data Protection for VMware
  environments, the TSM Client is also known as the data mover.
  Note 3: This is subject to change at the discretion of IBM.
  

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

• R71A PSY

     UP

• R71L PSY

     UP

• R71H PSY

     UP

• R71M PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP