Re: nfs_refresh_inode: inode number mismatch

From: Trond Myklebust (
Date: Thu Jul 19 2001 - 06:00:05 EST

>>>>> " " == Marco d'Itri <md@Linux.IT> writes:

> On Jul 17, Trond Myklebust <> wrote:
>> > Jul 18 00:15:07 newsserver kernel: nfs_refresh_inode: inode
>> > number mismatch Jul 18 00:15:07 newsserver kernel: expected
>> > (0x3b30ac75/0x48d5), got (0x3b30ac75/0x8d04)

>> If, on the other hand, you're using a clean kernel, I'd look
>> into what the server is doing. It sounds like it's doing the
>> same thing that the userland `nfs-server' does: namely to
>> recycle filehandles after a file gets deleted...
> Anything specific I can tell to their tech support?

> Can I ignore these messages or I risk data corruption?

There's always a small danger of data corruption, since the NFS client
can't rely on the file handle actually being a pointer to the file we

Try 2.4.6 first though, as a couple of fixes were implemented there
that should reduce the frequency of such messages. Basically we ensure
that inodes are removed from the cache when we do believe that it has
been deleted.

A proper fix, though, would be for the server to implement filehandles
that are unique as per RFC1813...

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

This archive was generated by hypermail 2b29 : Mon Jul 23 2001 - 21:00:11 EST