[lkml]   [1998]   [Sep]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: nfs_lookup_revalidate: %s fh changed

On Thu, 24 Sep 1998, Bill Hawes wrote:

> 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?

Yes, the mismatch messages are always on transient files which may very
well have changed underneath.

Glad to know that these things are not really problems (breathing big sigh
of relief).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.045 / U:0.616 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site