Date: Mon, 14 Apr 1997 14:57:56 -0400 (EDT) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: update on 2.2.1 NFS problems... (my debugging...) Message-ID: <199704141857.OAA25971@lakes.water.net>
next in thread | raw e-mail | index | archive | help
I've been putting printf()s in my kernel to try and determine
where my NFS is locking up.
Well - it has wound it's way all the way down to soreceive().
Apparently, it's going like this:
1) nfs_readdirrpc() calls nfsm_request() [toward the top of nfs_readdirrpc().
2) nfs_request calls nfs_send() to send the request, and then
calls nfs_reply to wait on the reply.
3) nfs_reply calls nfs_receive() which, since this is simply
a "normal" NFS (not TCP), jumps down to do an soreceive().
4) soreceive() locks up.
This, of course, explains why the "ls -l" process that causes
this is handing in "sbwait"...
[On another note, eventually, of course, the kernel times out this request
and you get "nfs server XXX:/filesystem: not responding" - but that
time out seems to take a *lot* longer than the -t option would indicate...]
This would seem to be a rather generic socket issue - has anyone
got any ideas?
- Dave Rivers -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704141857.OAA25971>