IJ45806: .PTRASH LOCAL BIT GETTING RESET CAUSING DANGLING ENTRIES IN RO/LU/IW MODES OR RECOVERY ISSUES IN SW/DR/IW

APAR status

• Closed as program error.

Error description

• There is a peculiar case where the local bit on the .ptrash
  directory inside AFM filesets gets reset. This causes the
  .ptrash directory to be treated like a normal directory and in
  Write modes, the temporary files generated for recovery/resync
  policy start getting replicated to the remote site. For Read
  modes this causes the ptrash directory to show up as a dangling
  entry because a normal lookup is sent to home - and since the
  .ptrash doesn't have remote attrs - it fails to complete this
  lookup successfully. This also causes errors when the user wants
   to empty the ptrash with rm -rf since the lookups to remote
  site don't succeed.
  

Local fix

• Manually set the local bit on ptrash on seeing issues
  

Problem summary

• There is a peculiar case where the local bit on the .ptrash
  directory inside AFM filesets gets reset. This causes the
  .ptrash directory to be treated like a normal directory and in
  Write modes, the temporary files generated for recovery/resync
  policy start getting replicated to the remote site. For Read
  modes this causes the ptrash directory to show up as a dangling
  entry because a normal lookup is sent to home - and since the
  .ptrash doesn't have remote attrs - it fails to complete this
  lookup successfully. This also causes errors when the user wants
   to empty the ptrash with rm -rf since the lookups to remote
  site don't succeed.
  

Problem conclusion

• This problem is fixed in 5.1.7.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:
  Avoid all ptrash local bit reset related miseries like not being
  able to remove ptrash contents (to make space in fileset) or
  recovery/resync mishaps that lead to unwanted messages being
  queued and showing errors.
  
  Work around:
  Manually set the local bit on ptrash on seeing issues.
  
  Problem trigger:
  ptrash local bit getting reset unintentionally and follow up
  operations performed on the fileset - like ls or recovery
  
  Symptom:
  Unexpected Behavior
  
  Platforms affected:
  All Linux OS environments (AFM Gateway nodes)
  All OS Platforms (Application nodes in AFM enabled clusters)
  
  Functional Area affected:
  AFM
  
  Customer Impact:
  High Importance
  

Temporary fix

Comments

APAR Information

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

  IJ45776

• 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