RFC: should an incremental reload of exports for mountd be optional?

Rick Macklem rmacklem at uoguelph.ca
Tue Jun 4 02:03:09 UTC 2019


Alan Somers wrote:
>On Mon, Jun 3, 2019 at 6:30 PM Rick Macklem <rmacklem at uoguelph.ca> wrote:
>>
>> Alan Somers wrote:
>> >Will a restart of the daemon cause clients to get HUPped if they try
>> >to access an exported filesystem while mountd is restarting?
>> >-Alan
>> I'm not sure what you mean by HUPped, but during a restart of mountd, extant
>> mounts should continue to work.
>
>Perhaps it wasn't SIGHUP, but I recall that a few years ago there was
>a problem where all NFS I/O would fail while mountd was reloading.  I
>think it's the problem that you fixed in r241568.
So long as the "-S" option is being specified, there shouldn't be a problem.

With "-S" both the initial load when started/restarted and a reload due to SIGHUP
will suspend the nfsd threads while deleting/loading exports in the kernel.
The patch just committed was mainly to make the duration of suspension during
a reload much shorter.

rick
[stuff snipped]


More information about the freebsd-fs mailing list