On Thu, Jan 10, 2008 at 11:59:51PM -0500, Bob Bell wrote:
In testing, we're seeing a problem where an ls of a directory over NFSv3
reports "File not found" for one of the sub-directories. With some
tracing turned on, I can see that there is an -EBADCOOKIE error returned
from find_dirent(). The error is persistent; it doesn't go away with
time. I do have one report that says that by adding another file to the
directory, the error went away.
...
My apologies, apparently EBADCOOKIE has nothing to do with this. The
problem is the caching model and ext3's full-second timestamp
granularity. I've already discussed the issue with Trond.
-- Bob
-
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
