IT33787: CLIENT JOURNAL-BASED BACKUP DAEMON (TSMJBBD) CRASHES

APAR status

• Closed as program error.

Error description

• The Journal-Based Backup (JBB) daemon can core dump when it's
  
  include-exclude processing encounters any kind of object
  name
  such as a file, directory, or symbolic link that contain
  
  invalid multibyte character.
  
  For example, use the following
  command to list a directory name
  that contains an invalid
  multibyte character (piped through the
  Linux hexdump command):
  
  # ls -d affected_dir_name | hexdump -ve '1/1 "%.2x"'
  
  The
  output will produce the hex values such as the following
  three
  byte sequence " ef 80 a9 ", where the hex value of the invalid
  
  multibyte character will be greater than the standard ASCII
  
  character set range of 0x00 - 0x7F.
  
  Note the core dump is
  triggered by an attempt to either remove
  or rename the affected
  object.
  
  The core dump contains the follow core stack:
  
  #0
  0x00007ff28bc4a8df in raise () from /lib64/libc.so.6
  #1
  0x00007ff28bc34cf5 in abort () from /lib64/libc.so.6
  #2
  0x00007ff28bc8dc17 in __libc_message () from
  
  /lib64/libc.so.6
  #3 0x00007ff28bc9453c in malloc_printerr ()
  from
   /lib64/libc.so.6
  #4 0x00007ff28bc94bf6 in
  unlink_chunk.isra () from
   /lib64/libc.so.6
  #5
  0x00007ff28bc95e8b in _int_free () from /lib64/libc.so.6
  #6
  0x00000000004095a7 in dsmFree(void*, char*, unsigned int) ()
  #7
  0x0000000000426317 in Match(char const*, unsigned long,
   char
  const*, unsigned long, char, char, int) ()
  #8
  0x0000000000426249 in Match(char const*, unsigned long,
   char
  const*, unsigned long, char, char, int) ()
  #9
  0x000000000042a62f in IsObjectExcluded(char*) ()
  #10
  0x000000000043a4a4 in psFsMonitorThread(void*) ()
  #11
  0x00007ff28d1372de in start_thread () from
  
  /lib64/libpthread.so.0
  #12 0x00007ff28bd0f133 in clone () from
  /lib64/libc.so.6
  
  Initial Impact:
  Medium - The probability of
  hitting this issue are very low.
  
  Tivoli Storage Manager
  Versions Affected:
  All currently supported JBB versions on AIX
  and Linux platforms are affected.
  
  Additional Keywords:
  
  TS003441335 "Spectrum Protect" core dump crash JBB
  

Local fix

• Find and rename the invalid multibye object names. Do not use
  or
  comment out any existing [JournalExcludeList] stanza in
  your
  tsmjbbd.ini file.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect backup-archive client versions 7.1.x    *
  * and 8.1.x on AIX and Linux platforms.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is projected *
  * to be fixed in level 7.1.8.10 and 8.1.11. Note that this is  *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• Upon the fix, instead of getting a core dump, the tsmjbbd daemon
  should appropriately handle objects whose names contain an
  incorrect multibyte character.
  

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

• tsmjbbd
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels