I thought setting the low percentage (FD_LWMark_Percent) to zero makes it close all anonymous fds periodically. Also, Madhu from IBM has a patch with a config setting where NFS-Ganesha opens and closes temp/anonympus fds without caching them at all. You may hit a perf hit for not cashing fds based on your FSAL/fs implementation though.
Okay, I understand the reasoning. This is inherently impossible with
NFSv4, since the protocol specification itself requires that FDs remain
open as long as the client is using them. Similarly, it's impossible
with any kind of locking (either NFSv3 or NFSv4), since, on linux, you
must keep your FD open for the lock to continue to exist.
For straight, non-locking NFSv3, it's possible, but it's not currently
implemented. The FD closing threads in Ganesha are not designed to
close all anonymous FDs, but rather to keep the number of open anonymous
FDs low. Work could be done to close them all, but no code exists
currently.
Daniel
On 12/19/20 11:45 AM, gershon geva wrote:
> Hi Daniel,
>
> We run Ganesha on top of our proprietary filesystem WekaFS. Some of our filesystem background cleanup tasks requires that all FDs on a given export be closed. Our current NFS implementation closes all open anonymous FDs after a pre-configured time period and allow those tasks to run when the NFS activity is relatively idle. We wish to have more or less the same behavior with Ganesha.
> _______________________________________________
> Support mailing list -- support@lists.nfs-ganesha.org
> To unsubscribe send an email to support-leave@lists.nfs-ganesha.org
>
_______________________________________________
Support mailing list -- support@lists.nfs-ganesha.org
To unsubscribe send an email to support-leave@lists.nfs-ganesha.org