IBM Support

IJ53560: FILE SYSTEM CANNOT BE RECOVERED AFTER SGPANIC FOLLOWED BY UNMOUNT.

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

  • Upon hitting SGPanic (due to OOS (Out Of Space) at the physical
    device(s)) in the file system with FCMs, there is (high)
    possibility that the diskSpaceState stays in DSS_OOS after the
    emergency space released.
    

Local fix

Problem summary

  • Upon hitting SGPanic (due to OOS (Out Of Space) at the physical
    device(s)) in the file system with FCMs, there is (high)
    possibility that the diskSpaceState stays in DSS_OOS after the
    emergency space released.
    

Problem conclusion

  • This problem is fixed in 5.2.2.1
    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:
    With the fix, the diskSpaceState will be transitioned properly
    (from DSS_OOS to DSS_Critical) upon releasing the emergency
    space.
    
    Work Around:
    None
    
    Problem trigger:
    On a file system with FCM 4, fill up the file system until all
    physical capacity is used so that it can trigger SGPanic due to
    OOS (Out Of Space) condition.
    
    Symptom:
    After the file system suffers with SGPanic, it will be
    unmounted. For recovery, the file system will be mounted in
    'restricted' mode and the emergency space will be release (with
    'mmreclaimspace <fs> --emergency-reclaim' command). However,
    after the emergency space is released, the file system would
    stay DSS_OOS as oppose to the expectation. Because of this, the
    file system can't be mounted in 'space-reclaim' mode which is a
    step required for the recovery.
    
    Platforms affected:
    Linux
    
    Functional Area affected:
    thin-provisioning
    
    Customer Impact:
    High Importance
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ53560

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    522

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-02-07

  • Closed date

    2025-02-19

  • Last modified date

    2025-02-19

  • 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":"BU048","label":"IBM Software"},"Product":{"code":"STXKQY"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"522","Line of Business":{"code":"LOB69","label":"Storage TPS"}}]

Document Information

Modified date:
19 February 2025