Trond Myklebust <trond.myklebust@fys.uio.no> writes:
> >>>>> " " == Jeff Garzik <jgarzik@mandrakesoft.com> writes:
>
> > After unsuccessfully trying to copy an ISO from a 2.2.15-pre17
> > SMP box (Dual PII/Asus) to a 2.3.99-pre4-pre3 K6/UP box (Via),
> > I rebooted the K6 box into 2.2.15-pre17.
>
> > In the process, the NFS client on the 2.2.x SMP box got really
> > confused when I typed 'df':
>
> > Apr 4 15:52:49 rum kernel: nfs_statfs: statfs error = 116 Apr 4
>
> error 116 == -ESTALE. This means that the file handle you were using
> against the 2.3.99 server is different from what the 2.2.15 kernel
> understands. This seems like a quite reasonable assumption. Why do you
> assume that it should succeed?
I've also seen that from time to time. I never managed to get a
tcpdump trace though.
It occurs when the NFS server is rebooted while some process on the
client has its current directory on the NFS-exported tree. Once the
server has completed the reboot, the client might get these errors.
An other annoyance is that hard-mounts do not behave properly: if I
try to access files on the NFS-exported directory while the server is
booting and the server's TCP/IP stack is up, but knfsd is not started
yet, then I get "connection refused" errors.
Phil.
-
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/
This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:13 EST