IJ26356: CAN NOT FIND THE NEW FILE WHEN RECEIVING DMAPI POSTRENAME EVENTS

APAR status

• Closed as program error.

Error description

• When a data management application receives a
  DMAPI postrename event, it fails to get the file handle
  for the renamed file with a "no such file" error. This is
  because Spectrum Scale is delivering a DMAPI
  postrename event before the Linux kernel updates
  its directory lookup cache for the file being renamed.
  

Local fix

• Let your data management application take a short sleep and
  retry to get the file handle of the renamed file name.
  

Problem summary

• When a data management application receives a
  DMAPI postrename event, it fails to get the file handle
  for the renamed file with a "no such file" error. This is
  because Spectrum Scale is delivering a DMAPI
  postrename event before the Linux kernel updates
  its directory lookup cache for the file being renamed.
  

Problem conclusion

• Benefits of the solution:
  This is a short term fix which returns the renamed file
  handle through the DMAPI postrename event. The old
  parent directory handle is now redefined as the renamed
  file handle.   This occurs when the undocumented configuration
  option "returnFileHandleInPostRenameEvent" is turned on.
  By default, the configuration option is turned off and the
  behavior
  for the DMAPI postrename event is not changed. With this change,
  the data management applications doesn't need to send another
  DMAPI call to get the renamed file handle when receiving the
  postrename event.
  
  Work around:
   Let your data management application take a short sleep and
  retry to get the file handle of the renamed file name.
  
  Problem trigger:
  DMAPI enabled Spectrum Scale file system and a DMAPI postrename
  event.
  
  Symptom:
  The data management application gets a ENOENT
  error if they are trying to get the file handle for the
  renamed file immediately after receiving a
  DMAPI postrename event.
  
  Platforms affected: All Operating Systems
  
  Functional Area affected: DMAPI
  
  Customer Impact: Suggested
  

Temporary fix

Comments

APAR Information

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

  IJ26290

• 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