Currently, there's no way to do this. You can invalidate the metadata cache for a single object with an UP-call (the invalidate() call) but there is no way to recursively invalidate, and no UP-call to remove a handle-cache entry at all. This last would chancy anyway, since anything with a ref on that entry would keep it around regardless of any UP-call. However, once the underlying inode for an entry is gone, the first use of it will return ESTALE, causing the entry to be removed ASAP. Daniel On 07/25/2018 10:03 AM, sshaikh@commvault.com wrote:
Hi, I have a requirement in my FSM to invalidate the cache. While doing it I want to nfs-ganesha to drop any in-memory cache for the given export.
How can I inform nfs-ganesha to drop all in-memory caches for the given export?
Regards, Shahid Shaikh. _______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org