IT08842: DIRECTORIES/FILES ARE SKIPPED ON INCREMENTAL BACKUP WHEN SUBVOLUME IS A DIRECTORY ONLY IN A BTRFS FILE SYSTEM

TSM 7.1.2.x interim fix client downloads
IBM Spectrum Protectâ„¢ Client 7.1.3 Downloads and READMEs

APAR status

• Closed as program error.

Error description

• During incremental backup some files/directories are skipped if
  the subvolumes are directories rather than their own mount
  point.  Subvolumes always have their own device ids.
  The BA Clients current behavior is to back up data from a
  subvolume only if the subvolume is mounted as its own file
  system.
  
  Customer/L2 Diagnostics (if applicable)
  As an example
  # tree /svt1
  /svt1
  ??? file1
  ??? subvol
      ??? dir
      ?   ??? file_dir
      ??? file_sub
  
  Here is the BA client's behavior when  backing up the main file
  system
  
  dsmc inc /svt1
  
  Incremental backup of volume '/svt1'
  Directory-->                  22 /svt1/ [Sent]
  Normal File-->                 4 /svt1/file1 [Sent]
  Successful incremental backup of '/svt1'
  
  Here is BA client's behavior when  backing up the subvolume
  without virtualmountpoint
  
  dsmc inc /svt1/subvol
  
  Incremental backup of volume '/svt1/subvol'
  ANS1016I No eligible files matching '/svt1/subvol' were found.
  Successful incremental backup of '/svt1/subvol'
  
  A third scenario with the subvolume as a  VIRTUALMOUNTPOINT.
  
  dsm.sys:
  virtualmountpoint /svt1/subvol
  
  dsmc inc /svt1/subvol
  
  Incremental backup of volume '/svt1/subvol'
  Directory-->                  22 /svt1/subvol/ [Sent]
  Normal File-->                10 /svt1/subvol/file_sub [Sent]
  Successful incremental backup of '/svt1/subvol'
  
  dsmc q files
    #     Last Incr Date          Type    File Space Name
  ----------------------------------------------------------------
  ----------------
    1     05/01/2015 08:58:59     BTRFS   /svt1
    2     05/01/2015 08:59:09     BTRFS   /svt1/subvol
  
  The, /svt1/subvol is backed up as its own file space, and a file
  directly underneath /svt1/subvol is also backed up, but the
  directory /svt1/subvol/dir and its content was not backed up as
  expected.
  
  *NOTE*
  "btrfs subvolume list <path>" displays information about
  existing subvolumes
  
  Platforms affected:
  Linux  7.x  x86, zSeries, pSeries
  
  Initial Impact: High
  
  Additional Keywords:  TSM ZZ63 ZZ71
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Tivoli Storage Manager for Client versions 7.1 running on    *
  * all Linux platforms                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 7.1.3.                        *
  * Note that until these levels are available, this information *
  * is subject to change at the discretion of IBM.               *
  ****************************************************************
  *
  

Problem conclusion

• The problem has been fixed so that it no longer occurs.
  

Temporary fix

• A fix for this problem is currently targeted for 7.1.2.2 interim
  fix package. Until this interim fix is actually available this
  information 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

• R71L PSY

     UP