IBM Support

IJ25856: OFFLINE FSCK SHOWS FALSE POSITIVE REPORT ABOUT DIRECTORY ENTRY POINTING TO A DELETED INODE.

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

  • While deleting files spectrum scale internally also
marks the files as free in its inode allocation map so
that it can be reused. But if the process is interrupted
(maybe due to some nodes going down) then in some
cases that can cause the files to not show as in use in the
inode allocation map even though they are not deleted. And
in such cases if offline fsck is run then fsck can show false
positive report about directory entry pointing to deleted inode.
For example:
file entry inode 553063
"file_name_13_for_tortDir_dirBlockSplits.tid4338.idx1.xxxxxxxxxx
xxxx"

Local fix

  • None required as the files were intended to be
deleted by the user, so there is no harm if fsck
repair deletes them.

Problem summary

  •  While deleting files spectrum scale internally also
marks the files as free in its inode allocation map so
that it can be reused. But if the process is interrupted
(maybe due to some nodes going down) then in some
cases that can cause the files to not show as in use in the
inode allocation map even though they are not deleted. And
in such cases if offline fsck is run then fsck can show false
positive report about directory entry pointing to deleted inode.
For example:
file entry inode 553063
"file_name_13_for_tortDir_dirBlockSplits.tid4338.idx1.xxxxxxxxxx
xxxx"

Problem conclusion

  • Benefits of the solution:
Offline fsck will not show false positive report
about directory entry pointing to a deleted inode.

Work around:
None required as the files were intended to be
deleted by the user, so there is no harm if fsck
repair deletes them.

Problem trigger:
Deleting of files getting interrupted due to
node assert/crashes.

Symptom:
False positive fsck report

Platforms affected:
ALL Operating System environments

Functional Area affected:
FSCK

Customer Impact:
Suggested

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IJ25856
    • 

  • Reported component name
    SPEC SCALE STD
    • 

  • Reported component ID
    5737F33AP
    • 

  • Reported release
    505
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2020-06-29
    • 

  • Closed date
    2020-06-29
    • 

  • Last modified date
    2020-06-29
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    
IJ25827
    

    • 

  • 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","label":"IBM Spectrum Scale"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"505","Line of Business":{"code":"LOB26","label":"Storage"}}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            30 June 2020
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback