> Well, nothing to shout about. I did the debug and got a rather large
> messages file very quickly. Checked the end when the error occured, and
> all it said was:
>
> Jul 28 21:16:17 bofh kernel: NFS: revalidating ///, ino=266112
> Jul 28 21:16:17 bofh kernel: NFS call getattr
> Jul 28 21:16:17 bofh kernel: RPC: attrstat status 0
> Jul 28 21:16:17 bofh kernel: RPC: attrstat OK type 2 mode 40777 dev
> 800007 ino 40f80
> Jul 28 21:16:17 bofh kernel: NFS reply getattr
> Jul 28 21:16:17 bofh kernel: NFS: refresh_inode(3/266112 ct=1)
> Jul 28 21:16:17 bofh kernel: NFS: /// revalidation complete
> Jul 28 21:16:17 bofh kernel: NFS: put_inode(3/266112)
> Jul 28 21:16:17 bofh kernel: NFS: delete_inode(3/266112)
>
> Not exactly enlightning to me. The strace wasn't any better...
I don't see any indication of an error there.
> read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 4096
> write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 4096
> read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 4096
> write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = -1 EIO
> (Input/output error)
The strace shows an error return, but nothing from NFS.
Did this just start happening recently? The NFS client hasn't changed much lately
...
> I guess I should mention that this is a 2.1.111 client hitting a Solaris
> 2.6 server...
Testing with a different server might provide some info on the problem.
Regards,
Bill
-
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.altern.org/andrebalsa/doc/lkml-faq.html