Can I force nfs client to perform lookup till current working directory? (trough error codes?) about nfs4j HOT 3 CLOSED

NFS spec assumes, that file handles are permanent. My guess will be as well to return ESTALE to enforce lookup. However, for directories this will mess-up client-side cache. May we you can try to implement persistent mapping with ehcache of hazelcast?

from nfs4j.

Thanks for the reply. I think I will try some persistent caching, but for now I'll check other options. I was wondering what kind of cache native Linux NFS client/server are using - persistent or in-memory.

from nfs4j.

I was unable to make client reload the cache, so I was forced to resolve the issue on the server side. As the VFS I'm using is relatively linked Parent->Child, I was able to store small portion of this relation in the Inode. When I receive Inode that's not in the cache, I perform manual lookups based on stored relations. For now this solves the issue, but if I run out of space in the Inode, there is no other option than storing mapping in persistent cache.

from nfs4j.