IJ42360: GANESHA: NFS CLIENT MIGHT GET NLM_DENIED OR NLM_BLOCKED AFTER AN

APAR status

• Closed as program error.

Error description

• When one CES node gets rebooted, NFS client lock requests
  might fail with a "NLM_DENIED" error.
  

Local fix

•  None in NFSv3. Issue not present in NFSv4.
  So one work around can be using NFSv4 instead of NFSv3.
  

Problem summary

• When one CES node gets rebooted, NFS client lock requests
  might fail with a "NLM_DENIED" error. i
  

Problem conclusion

• This problem is fixed in 5.1.5 PTF 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:
  NFS client subsequent lock requests (after
  lock reclaim and unlock requsets) will succeed.
  
  Work around: None in NFSv3. Issue not present in NFSv4.
  So one work around can be using NFSv4 instead of NFSv3.
  Problem trigger:
  When one of the protocol nodes of the cluster gets
  rebooted or a failover happens and a lock request is
  attempted on the same file
  Symptom:  Lock request will fail (NLM_DENIED or NLM_BLOCKED
  error can be seen in tcpdump reply frame of LOCK Request)
  Platforms affected: ALL Operating System environments
  Functional Area affected: NFS-Ganesha
  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