IBM Support

IJ46536: AFM RECOVERY FAILS WITH ERROR 22

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

  • When initial sync is triggered for a GPFS fileset (resync in
    progress) which is converted to AFM DR, none of the files/dirs
    have pcache remote or pcache parent EAs on the inode. If the
    initial sync is interrupted (and workload causes some
    remove/rename kind of operations on the local directories), then
     there are dirty directories at primary for which
    dirtyDirDirents policy scan is run to list all dirty dir
    entries. But for files which don't have state, the policy scan
    gives 5 fields as compared to 8 expected and results in recovery
     failing with error 22 (E_INVAL).
    

Local fix

  • Set afmSkipResyncRecovery to yes on the fileset and trigger
    recovery.
    

Problem summary

  • When initial sync is triggered for a GPFS fileset (resync in
    progress) which is converted to AFM DR, none of the files/dirs
    have pcache remote or pcache parent EAs on the inode. If the
    initial sync is interrupted (and workload causes some
    remove/rename kind of operations on the local directories), then
     there are dirty directories at primary for which
    dirtyDirDirents policy scan is run to list all dirty dir
    entries. But for files which don't have state, the policy scan
    gives 5 fields as compared to 8 expected and results in recovery
     failing with error 22 (E_INVAL).
    

Problem conclusion

  • This problem is fixed in 5.1.2.11
    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:
    AFM Recovery shall not fail with error 22.
    
    Work around:
    Set afmSkipResyncRecovery to yes on the fileset and trigger
    recovery.
    
    Problem trigger:
    Running AFM recovery on an AFM DR Fileset who's initial sync has
    never completed.
    
    Symptom:
    Unexpected Results
    
    Platforms affected:
    All Linux OS Environments (Serving as AFM Gateway nodes)
    
    Functional Area affected:
    AFM
    
    Customer Impact:
    High Importance
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ46536

  • 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

    2023-04-21

  • Closed date

    2023-05-03

  • Last modified date

    2023-05-03

  • 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:
03 May 2023