Messages in this thread | | | Subject | Re: nfs_refresh_inode: inode number mismatch | From | Trond Myklebust <> | Date | 17 Jul 2001 11:44:57 +0200 |
| |
>>>>> " " == Marco d'Itri <md@Linux.IT> writes:
> 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 patches (availalble from my WWW-page, but clearly marked experimental) was generating these messages gratuitously.
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...
Cheers, Trond - 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/
| |