From owner-freebsd-stable@FreeBSD.ORG  Mon Oct 25 09:25:51 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 51C8516A4CE
	for <freebsd-stable@freebsd.org>;
	Mon, 25 Oct 2004 09:25:51 +0000 (GMT)
Received: from grummit.biaix.org (86.Red-213-97-212.pooles.rima-tde.net
	[213.97.212.86])	by mx1.FreeBSD.org (Postfix) with SMTP id 2012143D2D
	for <freebsd-stable@freebsd.org>;
	Mon, 25 Oct 2004 09:25:50 +0000 (GMT)
	(envelope-from lists-freebsd-stable@biaix.org)
Received: (qmail 40445 invoked by uid 1000); 25 Oct 2004 09:23:30 -0000
Date: Mon, 25 Oct 2004 11:23:30 +0200
From: Joan Picanyol <lists-freebsd-stable@biaix.org>
To: Robert Watson <rwatson@FreeBSD.org>
Message-ID: <20041025092330.GB39457@grummit.biaix.org>
Mail-Followup-To: Robert Watson <rwatson@FreeBSD.org>,
	freebsd-stable@freebsd.org
References: <20041025002008.GA36161@grummit.biaix.org>
	<Pine.NEB.3.96L.1041025093648.91675C-100000@fledge.watson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.NEB.3.96L.1041025093648.91675C-100000@fledge.watson.org>
User-Agent: Mutt/1.4.1i
cc: freebsd-stable@freebsd.org
Subject: Re: process stuck in nfsfsync state
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2004 09:25:51 -0000

* Robert Watson <rwatson@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
it...

> > 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@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.

tks
-- 
pica