IBM Support

IJ33419: MANUAL RESYNC COMMAND SHOULD RECLAIM DELETED INODES FOR REUSE

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

  • mmafmctl command has a provision to reclaim deleted
    inodes when Resync is manually run.
    This causes the inodes to be reclaimed only under
     some conditions and not reclaimed in other cases.
    

Local fix

  • 1. A full resync and then recovery needs to be run in order to
        reclaim deleted inodes.
    
    2. A resync with afmSkipResyncRecovery at the cluster level
        tuned using the mmchconfig command should be run..
       Fileset level tuned doesn't work today.
    
    3. Worst case an mmfsck needs to be run to reclaim the inodes.
    

Problem summary

  • mmafmctl command has a provision to reclaim deleted
     inodes when Resync is manually run.
    This causes the inodes to be reclaimed only under
     some conditions and not reclaimed in other cases.
    

Problem conclusion

  • This problem is fixed in 5.1.1  PTF 2
    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:
    Manual Resync run through the mmamctl command will
     be able to reclaim those
     deleted inodes which are awaiting replication
     to the remote site.
    
    Work around:
    1. A full resync and then recovery needs to be run in order to
        reclaim deleted inodes.
    
    2. A resync with afmSkipResyncRecovery at the cluster level
        tuned using the mmchconfig command should be run..
       Fileset level tuned doesn't work today.
    
    3. Worst case an mmfsck needs to be run to reclaim the inodes.
    
    Problem trigger:
    Running manual resync on fileset without recovery, with
     afmSkipResyncRecovery flag set on the fileset level.
    
    Symptom:
    Unexpected Behavior
    
    Platforms affected:
    ALL Linux OS environments
     (acting as AFM Gateway node)
    
    Functional Area affected:
    AFM
    
    Customer Impact:
    Suggested
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ33419

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    511

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-06-25

  • Closed date

    2021-06-25

  • Last modified date

    2021-06-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":"511"}]

Document Information

Modified date:
26 June 2021