IJ42737: NEWLY CREATED NFS EXPORTS NOT VISIBLE ON FEW NODES

APAR status

• Closed as program error.

Error description

• Newly created NFS exports are not accessible from few CES
  nodes and NFS service has to be restarted for the exports
  to be accessible from these node.
  

Local fix

• Create export failed in resolve_posix_filesystem().The
  issue is due Ganesha NFS not repopulating posix
  filesystem
  while creating export path  and this is happening if
  there
  is a change in mounted FS order and new export path reuse
  the device number of old mount point
  

Problem summary

• NFS fails to resolve the posix filesystem, when a 'tmpfs'
  type is mounted prior to adding any gpfs export,
  and then unmounted. This happens because NFS does not
  repopulate the posix filesystem which leads to
  mismatch of major and minor number of exports
  

Problem conclusion

• This problem is fixed in 5.1.2 PTF 8
  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:
  Newly created exports will be visible from NFS clients.
  
  Work around:
  Restart NFS ganesha incase there is major/minor number
  mismatch of the filesystems
  Problem trigger:
  tmpfs filesystem remains in the posix list maintained
  by NFS; the list which is not re-populated
  for every new export add.
  Symptom:
  Newly created exports will not be visible on NFS clients
  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 DME

• Fixed component ID

  5737F34AP

Applicable component levels