IT36771: CLIENT CRASHES DURING PARTIAL INCREMENTAL BACKUP WHEN DUPLICATE CASE SENSITIVE DIRECTORY OBJECTS EXIST IN THE SAME PATH

APAR status

• Closed as program error.

Error description

• The backup-archive client crashes during partial incremental
  backup when some duplicate case sensitive directory objects are
  in the path to be saved.
  Here are two examples of a stack trace from the dsmcrash.log
  file when that problem happens:
  
  Example 1:
  
   dsmc.exe, dtGetNext()+119 bytes
   dsmc.exe, ProcList()+1990 bytes
   dsmc.exe, PrivIncrFileSpace()+2950 bytes
   dsmc.exe, PrivIncrFileSpace()+4056 bytes
   dsmc.exe, PrivIncrFileSpace()+4056 bytes
   dsmc.exe, PrivIncrFileSpace()+4056 bytes
   dsmc.exe, PrivIncrFileSpace()+4056 bytes
   dsmc.exe, baIncremental()+2399 bytes
   dsmc.exe, baProcessRequest()+3704 bytes
   dsmc.exe, baRequestHandler()+1582 bytes
   dsmc.exe, DccTxnProducer::HandleQueue()+587 bytes
   dsmc.exe, DccTxnProducer::Run()+1374 bytes
   dsmc.exe, startThread()+279 bytes
   ucrtbase.dll, o_exp()+90 bytes
   KERNEL32.DLL, BaseThreadInitThunk()+20 bytes
   ntdll.dll, RtlUserThreadStart()+33 bytes
  
  Example 2:
  
   dsmc.exe, StriCmp()+72 bytes
   dsmc.exe, AddFN()+296 bytes
   dsmc.exe, dtInsFile()+223 bytes
   dsmc.exe, FillDirTree2()+3017 bytes
   dsmc.exe, FillDirTree()+98 bytes
   dsmc.exe, PrivIncrFileSpace()+2744 bytes
   dsmc.exe, PrivIncrFileSpace()+4056 bytes
   dsmc.exe, PrivIncrFileSpace()+4056 bytes
   dsmc.exe, PrivIncrFileSpace()+4056 bytes
   dsmc.exe, PrivIncrFileSpace()+4056 bytes
   dsmc.exe, BaIncremental()+2399 bytes
   dsmc.exe, baProcessRequest()+3704 bytes
   dsmc.exe, baRequestHandler()+1582 bytes
   dsmc.exe, DccTxnProducer::HandleQueue()+587 bytes
   dsmc.exe, DccTxnProducer::Run()+1374 bytes
   dsmc.exe, startThread()+279 bytes
   ucrtbase.dll, o_exp()+90 bytes
   KERNEL32.DLL, BaseThreadInitThunk()+20 bytes
   ntdll.dll, RtlUserThreadStart()+33 bytes
  
  Customer/Support Diagnostics:
  
  Here is an example of the filesystem subtree details where this
  issue would be seen:
  
   Two directories are in the same parent directory with only one
  different cased character with same object stored inside.
  
   Directory of \\hostname\path1\path2\
    <DIR> .
    <DIR> ..
    <DIR> dir_with_Sensitive_case
    <DIR> dir_with_sensitive_case
  
   Directory of \\hostname\path1\path2\dir_with_Sensitive_case
  
    <DIR> .
    <DIR> ..
         40 file1.xx
         40 file2.xx
  
   Directory of \\hostname\path1\path2\dir_with_sensitive_case
    <DIR> .
    <DIR> ..
         40 file1.xx
         40 file2.xx
  
  IBM Spectrum Protect Versions Affected:
   Backup-archive client 7.1 and 8.1 releases on Windows platform
  
  Initial Impact: Medium
  
  Additional Keywords: TS005263783 dump dmp TSM
  

Local fix

• Add the following option into the client's option file
  (dsm.opt ):
  
        CASESENSITIVEAWARE YES
  
    With that option set, the crash will not happen, and one of
    the case sensitive object or subtree will not be saved.
  
  https://www.ibm.com/docs/en/spectrum-protect/8.1.11?topic=refere
  nce-casesensitiveaware
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Backup-archive client versions 7.1 and 8.1 running on        *
  * Windows platforms.                                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * This issue is projected to be fixed in the backup-archive    *
  * client version 8.1.13 on Windows platforms.                  *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• The code has been fixed so currently the client allows to bypass
  the crashes via the testlag  DONTCHGMEMPOOL.
  

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 CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels