IBM Support

IJ49586: MMFSCKX WILL TAKE LONGER TO RUN ON FILE SYSTEMS HAVING LARGE NUMBER OF INDEPENDENT FILESETS

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

  • File systems that have large number independent filesets usually
    tend to have a sparse inode space.So if mmfsckx is run on such
    a file system having large sparse inode space then it will take
    longer to run as it unnecessarily parses over inode alloc map
    segments pointing to sparse inode spaces instead of skipping
    them.
    

Local fix

Problem summary

  • File systems that have large number independent filesets usually
    tend to have a sparse inode space.So if mmfsckx is run on such
    a file system having large sparse inode space then it will take
    longer to run as it unnecessarily parses over inode alloc map
    segments pointing to sparse inode spaces instead of skipping
    them.
    

Problem conclusion

  • This problem is fixed in 5.1.9.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:
    mmfsckx will complete faster on file systems having large number
    of independent filesets
    
    Work Around:
    None
    
    Problem trigger:
    Run mmfsckx on file systems having large number of independent
    filesets
    
    Symptom:
    Slowness to complete run
    
    Platforms affected:
    All
    
    Functional Area affected:
    FSCKX
    
    Customer Impact:
    High Importance
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ49586

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    519

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-12-22

  • Closed date

    2023-12-22

  • Last modified date

    2023-12-22

  • 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":"519","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
23 December 2023