> When the problem occurs, all processes that touch the mount are
> indefinitly hung. Errors in messages show up:
> Feb 24 18:08:04 dhp0020 kernel: nfs: server 192.168.0.253 not
> responding, still trying
> Feb 24 18:08:04 dhp0020 kernel: nfs: server 192.168.0.253 not
> responding, still trying
As far as its concerned the netapp isnt talking
> The problem is immediately solved with a simple umount -f; which fails
> because of the current processes, but it fixes the hang! When I do
> umount -f, all of the waiting processes get a failed read, but they
> continue normally.
That suggests a wakeup got missed somewhere. It doesnt fit the netapp
not talking. Either the netapp is losing a consistent request or it is
the nfs client in the kernel. Both are possible, only doing some network
dumps (tcpdump with -l 1514 and asked to decode NFS frames) done when it
starts hanging would tell
-
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 : Tue Feb 29 2000 - 21:00:18 EST