From owner-freebsd-fs@FreeBSD.ORG  Mon Aug  1 21:14:19 2005
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
X-Original-To: fs@freebsd.org
Delivered-To: freebsd-fs@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 19E5A16A41F
	for <fs@freebsd.org>; Mon,  1 Aug 2005 21:14:19 +0000 (GMT)
	(envelope-from rick@snowhite.cis.uoguelph.ca)
Received: from moe.cs.uoguelph.ca (moe.cs.uoguelph.ca [131.104.96.55])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C017743D45
	for <fs@freebsd.org>; Mon,  1 Aug 2005 21:14:18 +0000 (GMT)
	(envelope-from rick@snowhite.cis.uoguelph.ca)
Received: from snowhite.cis.uoguelph.ca (snowhite.cis.uoguelph.ca
	[131.104.48.1])
	by moe.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id j71LEFox028563;
	Mon, 1 Aug 2005 17:14:17 -0400
Received: (from rick@localhost)
	by snowhite.cis.uoguelph.ca (8.9.3/8.9.3) id RAA37699;
	Mon, 1 Aug 2005 17:14:45 -0400 (EDT)
Date: Mon, 1 Aug 2005 17:14:45 -0400 (EDT)
From: rick@snowhite.cis.uoguelph.ca
Message-Id: <200508012114.RAA37699@snowhite.cis.uoguelph.ca>
To: kris@obsecurity.org
X-Scanned-By: MIMEDefang 2.44
Cc: fs@freebsd.org, openbsd-nfsv4@sfobug.org
Subject: Re: Re: FreeBSD6.0-BETA1 panics
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2005 21:14:19 -0000

> It didn't panic yet, but when doing a multiple simultaneous cvs update
> with NFS3 mounted repo the clients eventually got stuck in the nfsreq
> state.
> 
> FreeBSD had a similar problem for a while, after a change made last
> December, but it was fixed early this year.  Is your server based on
> an old version of the freebsd server code that is missing this (and
> possibly other) fixes, or is this a new bug introduced in your
> version?

The short answer is that the low level socket handling code for the
FreeBSD port is pretty well cloned from the FreeBSD server,
so I'll take a look at the bugfix stuff on
the web site, to see what that was. I'll also check my code against the
current FreeBSD server stuff.

If you could email me the following on the server at the time of the
hang, it could be useful:
# netstat -a 		<-- to see if the connection has data in the
				send or rcv queue
# ps axl | fgrep newnfsd <-- to see if any are hung and where

Again, thanks for the testing, rick