An anonymous FD is one used by NFSv3 read/write (but not lock), or
explicitly as an anonymous FD in NFSv3. All normal NFSv4 I/O and all
locks in both protocols need to have FDs kept open for the duration of
the client operation.
It's not impossible to force close anonymous FDs, but why do you want to
do that? We close them in the background, and it's tunable with many
option in the MDCACHE block. What behavior do you need that the current
system doesn't provide?
Daniel
On 12/17/20 6:25 AM, gershon geva wrote:
What qualifies as an anonymous FD? and assuming we only refer to
those FDs, is it possible to configure a more aggressive background reaping process that
would close them all within a pre-configured time?
_______________________________________________
Support mailing list -- support(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org