Re: nfs_refresh_inode: inode number mismatch

Marco d'Itri (md@Linux.IT)
Thu, 19 Jul 2001 00:25:20 +0200


On Jul 17, Trond Myklebust <trond.myklebust@fys.uio.no> 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)

> > I've got a flood of these messages while talking to a procom
> > NAS this. Should I worry? Upgrade/patch the kernel? Yell at
> > procom tech support?

>Have you applied any extra patches to NFS? I remember one of my
No, the kernel is plain unpatched 2.4.5.

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

-- 
ciao,
Marco
-
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/