> I continue seeing problems with Linux 2.2.3 NFS client. I am editing text
> files under XEmacs. After long time working, I see that the files on the
> server are corrupted with NULLs at the start, or truncated to size 0.
> If I look at the files from the Linux client, they look OK. This message
> is logged:
>
> nfs_refresh_inode: mismatch, ino=3726, fattr=4085
> nfs_refresh_inode: mismatch, ino=3726, fattr=3610
> nfs_refresh_inode: mismatch, ino=3726, fattr=3610
The NFS server is, for some reason, returning a different fileid
('inode number') for your file. Usually this happens if the filehandle
goes stale on the server and is reused for a different file. In your
case, however, the filehandle seems to be still valid since it seems
to corrupt the correct file...
What server are you using?
Cheers,
Trond
-
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/