Commits on Nov 17, 2021

1. nfsd.service: Order after mxmount.service …

   Currently there is no order between nfsd.service and mxmount.service. If
   mxmount is slow (e.g. when file systems have to process their journals
   after a server crash), nfsd startup might execute `exportfs -ra` while
   the filesystems are not yet mounted, thereby exporting the unmounted
   mountpoints.
   
   This can result in mount failures on nfs clients or in "stale NFS
   handle" errors on clients, which had the filesystems mounted before the
   crash.
   
   mxmount.service uses `mxmount --noexport` so there is no reexport
   triggered, after the filesystems are mounted. nfsd.services executes
   additional `exportfs -ra` commands 10, 20 and 30 seconds after the nfsd
   startup, but 30 seconds might not be enough time to mount all
   filesystems after the crash of a fileserver.
   
   These errors can persist. They are partly resolved by a manual
   `exportfs -ra` after a longer time, making the file systems available
   for mounting. However, the "stale NFS handle" problem might still be
   visible on clients which picked up the now covered inodes of the
   mountpoints.
   
   Order nfsd.service after mxmount.service so that we don't export the
   mountpoints.

   

   donald committed Nov 17, 2021
   Configuration menu

   • View commit details
   • Copy full SHA for 2c7ad52
   • Browse repository at this point

   Copy the full SHA

   2c7ad52 View commit details

   Browse the repository at this point in the history