Messages in this thread | | | Subject | Re: NFS file handle cached incorrectly | From | Trond Myklebust <> | Date | Tue, 13 Apr 2004 09:57:30 -0700 |
| |
På ty , 13/04/2004 klokka 07:25, skreiv David Mansfield:
> I don't think this is quite correct. The 1 second or less gap is not > between two modifications of the directory. It is between the initial > lookup and a remote modification. The mtime IS being updated, it's > just not being checked. ie.
In my version of the patch (which I assume is what Steve grabbed) the first thing nfs_cached_lookup() does is to call nfs_revalidate_inode().
It may well be that the directory attribute cache has not timed out yet. If so, that will indeed cause the mtime not to be checked on the client. If this really is a problem for you, then I suggest you make the directory attribute caching less aggressive. 'man 5 nfs' and read up on "acdirmin/acdirmax".
Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |