IBM Support

IJ41831: THE MMBACKUP SHADOWDB FILE COULD CONTAIN DUPLICATE RECORDS IF A POLICY SCAN INITIATED BY MMBACKUP FAILS.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If a policy scan, initiated from the mmbackup command,
    fails and the mmbackup shadowDB file contains an entry
    for a file that was previously backed up but is now deleted,
    and the inode of that file has been
    assigned to a newly created file,
    then the mmbackup shadowDB file will
    have duplicate records for that file.
    

Local fix

  • Fix the root cause of policy scan failure and rebuild shadowDB.
    

Problem summary

  • If a policy scan, initiated from the mmbackup command,
    fails and the mmbackup shadowDB file contains an entry
    for a file that was previously backed up but is now deleted,
    and the inode of that file has been
    assigned to a newly created file,
    then the mmbackup shadowDB file will
    have duplicate records for that file.
    

Problem conclusion

  • This problem is fixed in 5.1.2 PTF 7
    To see all Spectrum Scale APARs and
    their respective fix solutions refer to page
    https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale_
    apars.html
    
    Benefits of the solution:
    The mmbackup command will properly handle the
    reassignment of an inode from a file
    with an entry in the shadowDB,
    which has been deleted, to a newly created file.
    
    Work around:
    Fix the root cause of policy scan failure and rebuild shadowDB.
    Problem trigger:
    This problem occurs under the following conditions:
     1. An entry exist in the mmbackup shadowDB
    for a file that has been deleted.
     2. The inode for the file described in condition 1 has been
    assigned to a newly created file that needs to be backed up.
     3. The policy scan done by mmbackup fails.
    Symptom:
    Component Level Outage
    Platforms affected:
    all platforms that support mmbackup
    Functional Area affected:
    mmbackup
    Customer Impact:
    High Importance
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ41831

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    512

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-08-25

  • Closed date

    2022-08-25

  • Last modified date

    2022-08-25

  • 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

    SPEC SCALE STD

  • Fixed component ID

    5737F33AP

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STXKQY"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"512","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
25 August 2022