IT25629: "REPAIR STGPOOL" DOES NOT REPAIR EXTENTS BUT ENDS IN SUCCESS

8.1.7.000-IBM-SPSRV-Linuxppc64le
8.1.7.000-IBM-SPCMS-WindowsX64
8.1.7.000-IBM-SPCMS-WindowsI32
8.1.7.000-IBM-SPCMS-Linuxx86_64
8.1.7.000-IBM-SPOC-WindowsX64
8.1.7.000-IBM-SPOC-Linuxx86_64
8.1.7.000-IBM-SPOC-Linuxs390x
8.1.7.000-IBM-SPOC-LinuxPPC64le
8.1.7.000-IBM-SPOC-AIX
8.1.7.000-IBM-SPSRV-WindowsX64
8.1.7.000-IBM-SPSRV-Linuxx86_64
8.1.7.000-IBM-SPSRV-Linuxs390x
8.1.7.000-IBM-SPSRV-AIX
IBM Spectrum Protect Server V8.1 Fix Pack 7 (V8.1.7) Downloads

APAR status

• Closed as program error.

Error description

• If there are damaged chunks that do not have a valid copy,
  REPAIR STGPOOL might report 0 repaired extents, but still ends
  in success.
  The following example is for a repair attempted from a local
  protect target copy pool.
  
  Q DAMAGED STGPOOLNAME TYPE=N
  might report damaged objects as with the following example:
  ANR4675W QUERY DAMAGED: This command may take a while to finish.
  
  Node Name                     Number of Damaged
                                             Files
  -------------------------     ------------------
  <NODENAME>                                     3
  
  If no valid copies for the damaged chunks are found, "REPAIR
  STGPOOL <POOLNAME> TARGE=LOCAL" reports something like:
  
  ANR4982I The repair storage pool process for <DAMAGEDPOOL> on
  server <SERVER1> from <PROTECTTARGET> on server <SERVER1> is
  complete. Extents repaired: 0 of 0. Extents
  failed: 0. Extents skipped: 0. Amount repaired: 0 bytes of 0
  bytes. Amount failed: 0 bytes. Amount skipped: 0 bytes. Elapsed
  time: 0 Days, 0 Hours, 0 Minutes.
  ANR0985I Process 167 for Repair Stgpool running in the
  FOREGROUND completed with completion state SUCCESS at 11:56:02.
  
  This can be confusing and the messages should indicate if there
  are damaged extents that do not have a valid copy so
  administrators can react accordingly.
  
  
    IBM Spectrum Protect Versions Affected: 7.1.2 and 8.1 on all
  supported platforms
  
    Customer/L2 Diagnostics (If Applicable)
    For repair from a pool locally protected a trace with
  traceflag SDREPAIR will not find any volume as source for the
  repair operation and only report
    [sdrepair.c][6277][LocalGetVolListForRepair]:Container volume
  28964( primary <DAMAGEDPOOLID>, copy -<<PROTECTTARGETID> ) has
  no chunk copies needed, not queued into repair list.
  
    Initial Impact: Low
  
    Additional Keywords: TS000979386 damaged chunks protect repair
  tsm
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Spectrum Protect server users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 8.1.7. Note that this is      *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms for reported release:  AIX, Linux, and
  Windows.
  Platforms fixed:  AIX, Linux, and Windows.
  

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 SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels