IJ45536: NFS RESTARTED AFTER A NODE REBOOT WHILE A NFS EXPORTED FILESYSTEM IS STILL UNMOUNTED

APAR status

• Closed as program error.

Error description

• Spectrum Scale and systemhealth monitor (sysmon) start
  independently after a node reboot.
  During initialization, Spectrum Scale checks if all declared NFS
  exports are available.
  The sysmon configuration has the flag
  "preventnfsstartuponmissingfs" enabled, so the expected behavior
  was that NFS is not started if a required filesystem is
  unmounted. But in fact, NFS was started anyway.
  

Local fix

• None
   Make sure that the exported filesystems have the automount
  feature enabled, if possible.
  If the missing exported filesystem is not in use anyway, then
  remove it from the declared export list.
  

Problem summary

• Spectrum Scale and systemhealth monitor (sysmon) start
  independently after a node reboot.
  During initialization, Spectrum Scale checks if all declared NFS
  exports are available.
  The sysmon configuration has the flag
  "preventnfsstartuponmissingfs" enabled, so the expected behavior
  was that NFS is not started if a required filesystem is
  unmounted. But in fact, NFS was started anyway.
  

Problem conclusion

• This problem is fixed in 5.1.2.10
  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 will not be started after reboot if the flags
  "preventnfsstartuponmissingfs" is set and a declared NFS export
  filesystem is not mounted. After a while of waiting (up to 15
  minutes for CES startup) mmhealth will show the NFS monitoring
  as in STOPPED state and NFS itself (Ganesha) is not running.
  
  Please note that the sysmon configuration value
  "validatedeclaredcesexports" must also be enabled to run those
  export validation checks.
  (See /var/mmfs/mmsysmon/mmsysmonitor.conf)
  
  Work Around:
  N/A - Make sure that the exported filesystems have the automount
  feature enabled, if possible.
  If the missing exported filesystem is not in use anyway, then
  remove it from the declared export list.
  
  Problem trigger:
  Spectrum Scale and systemhealth monitor (sysmon) start
  independently after a node reboot.
  During initialization, Spectrum Scale checks if all declared NFS
  exports are available.
  At that point in time the sysmon was still initializing and has
  not yet done this evaluation. So it returns "no bad
  configuration found" which triggers then the NFS startup.
  The sysmon configuration has the flag
  "preventnfsstartuponmissingfs" enabled, so the expected behavior
  was that NFS does not come up.
  Ganesha will fail later and trigger an IP address failover,
  which disturbs the cluster operation.
  
  Symptom:
  Unexpected Results/Behavior
  
  Platforms affected:
  ALL Linux OS environments running CES with enabled NFS protocol
  
  Functional Area affected:
  System Health
  
  Customer Impact:
  Medium Importance
  

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:

  IJ45803

Fix information

• Fixed component name

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels