IJ37231: NFSV4 RFC SERVER_SCOPE SHOULD BE CLUSTER NAME NOT HOSTNAME

APAR status

• Closed as program error.

Error description

• As per the NFSv4 RFC , the server_scope should be
  clustername or groupname which is common across all the
  ganesha nodes. But we are using hostname as server_scope
  and it is wrong.
  

Local fix

Problem summary

• As per the NFSv4 RFC , the server_scope should be
  clustername or groupname which is common across all the
  ganesha nodes. But we are using hostname as server_scope
  and it is wrong.
  

Problem conclusion

• This problem is fixed in 5.1.2  PTF 3
  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:
  Enable NFSv4 client continue I/O operation after CES-IP
  Failover.
  
  Work around: None
  Problem trigger:
  If NFSv4 client holds a file lock for write operation, then
  CES-IP
  failover from current active NFS server(lets say protocol node1)
  to
  other server (protocol node2) may cause I/O failure on client.
  Symptom: I/O error
  Platforms affected: ALL Operating System environments
  Functional Area affected: cNFS/ 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