process stuck in nfsfsync state
lists-freebsd-stable at biaix.org
Mon Oct 25 02:25:51 PDT 2004
* Robert Watson <rwatson at FreeBSD.org> [20041025 10:42]:
> On Mon, 25 Oct 2004, Joan Picanyol wrote:
> > [please honour Mail-Followup-To:, no need to keep the crosspost]
> Hmm. Don't see one of those, maybe it was trimmed by Mailman?
Just checked, must have been. Maybe because it only had -stable@ on
> > Also, doing 'tcpdump -vv -s 192 port nfs' on the client and the server
> > seems support the hypothesis of a locking issue, since I see a write
> > request for the same fh repeating over and over.
> Is there an response to the request? If not, that might suggest the
> server is wedged, not the client. If you are willing to share the results
> of a tcpdump -s 1500 -w <whatever> output from a few seconds during the
> wedge, that would be very useful.
Available at http://biaix.org/pk/debug/nfs/ These are from just after
logging in to GNOME until gconfd-2 goes to nfsfsync, and the nfs server
not responding messages start appearing.
> Also useful would be the output of "netstat -na | grep 2049" on the client
> and server
Nothing special, it's the same before and after the wedge (grummit is
the server, calvin the client):
calvin# netstat -na | grep 2049
udp4 0 0 192.168.124.9.943 192.168.124.1.2049
udp4 0 0 192.168.124.9.600 192.168.124.1.2049
joan at grummit:~(0)$ netstat -an | grep 2049
tcp4 0 0 *.2049 *.* LISTEN
udp4 0 0 *.2049 *.*
FYI, calvin is an SMP box, debug.mpsafenet=0 and the NIC is an xl.
More information about the freebsd-stable