IJ49372: PREVENT FILE OR DIRECTORY NOT FOUND ERROR ON WINDOWS DUE TO STALE NODE IN GPFS CACHE.

APAR status

• Closed as program error.

Error description

• When running a workload on Windows which creates and deletes
  lots of files anddirectories in a short span, the inode number
  assigned for GPFS objects may bereused. If a stale inode entry
  somehow persists in the GPFS cache due to in flighthold counts,
  it can happen that due to conflict between the old and new
  objecttypes, this stale entry will result in a file or directory
  not found error.
  

Local fix

Problem summary

• Problem description:
  When running a workload on Windows which creates and deletes
  lots of files anddirectories in a short span, the inode number
  assigned for GPFS objects may bereused. If a stale inode entry
  somehow persists in the GPFS cache due to in flighthold counts,
  it can happen that due to conflict between the old and new
  objecttypes, this stale entry will result in a file or directory
  not found error.
  

Problem conclusion

• This problem is fixed in 5.1.2.15
  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:
  Make inode number reuse more robust and prevent file or
  directory not found errors.
  
  Work Around:
  None
  
  Problem trigger:
  Running a workload on Windows which continuously creates and
  deletes lots of filesand directories quickly.
  
  Symptom:
  Unexpected Results/Behavior.
  
  Platforms affected:
  Windows/x86_64 only.
  
  Functional Area affected:
  All Scale Users.
  
  Customer Impact:
  Suggested.
  

Temporary fix

Comments

APAR Information

• 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