Messages in this thread | | | Date | Thu, 24 Sep 1998 17:14:01 -0700 | From | Bill Hawes <> | Subject | Re: nfs_lookup_revalidate: %s fh changed |
| |
Steven N. Hirsch wrote:
> Yes, absolute storms of them! I had to comment out the error reporting > code in fs/nfs/dir.c because the overhead of flushing the messages to the > system logs was bogging down the system. Like Olaf, I assumed they were > normal - and remained from your original alpha testing.
The "fh changed" messages don't indicate a problem and would occur with knfsd whenever it needs to get a new dentry for the file.
> I'm also seeing a flood of "inode mismatch" messages, but not in the same > order of magnitude as the "fh changed" ones <g>.
The inode should change only if the file in question was deleted and recreated with a new inode number. When you see these messages, are they for things like temp files that would only exist breifly?
Anyway, I think the messages can be removed; the revalidation code seems to be working just fine.
Regards, Bill
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |