From owner-freebsd-stable@FreeBSD.ORG  Mon Jul  3 10:50:09 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: 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 1B84816A40F
	for <freebsd-stable@freebsd.org>; Mon,  3 Jul 2006 10:50:09 +0000 (UTC)
	(envelope-from andrew@areilly.bpa.nu)
Received: from omta04sl.mx.bigpond.com (omta04sl.mx.bigpond.com
	[144.140.93.156])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F406A43D45
	for <freebsd-stable@freebsd.org>; Mon,  3 Jul 2006 10:50:07 +0000 (GMT)
	(envelope-from andrew@areilly.bpa.nu)
Received: from areilly.bpa.nu ([141.168.7.22]) by omta04sl.mx.bigpond.com
	with ESMTP
	id <20060703105005.FNHS7229.omta04sl.mx.bigpond.com@areilly.bpa.nu>
	for <freebsd-stable@freebsd.org>; Mon, 3 Jul 2006 10:50:05 +0000
Received: (qmail 89780 invoked by uid 501); 3 Jul 2006 10:50:09 -0000
Date: Mon, 3 Jul 2006 20:50:09 +1000
From: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org>
To: Robert Watson <rwatson@FreeBSD.org>
Message-ID: <20060703105009.GA89088@duncan.reilly.home>
References: <20060629230309.GA12773@lpthe.jussieu.fr>
	<20060630041733.GA4941@zibbi.meraka.csir.co.za>
	<cone.1151802806.162227.42680.1000@zoraida.natserv.net>
	<20060702162942.D1103@ganymede.hub.org>
	<cone.1151876984.69254.64011.1000@zoraida.natserv.net>
	<20060703042010.GG37822@deviant.kiev.zoral.com.ua>
	<cone.1151902211.613551.64011.1000@zoraida.natserv.net>
	<20060703045854.GH37822@deviant.kiev.zoral.com.ua>
	<20060703100038.I26325@fledge.watson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060703100038.I26325@fledge.watson.org>
User-Agent: Mutt/1.4.2.1i
Cc: Kostik Belousov <kostikbel@gmail.com>,
	Francisco Reyes <lists@stringsutils.com>,
	freebsd-stable@freebsd.org, User Freebsd <freebsd@hub.org>
Subject: Re: NFS Locking Issue
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
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, 03 Jul 2006 10:50:09 -0000

On Mon, Jul 03, 2006 at 10:06:52AM +0100, Robert Watson wrote:
> It sounds like there is also an NFS client race condition or other bug of 
> some sort.

It may not be related, directly, but one thing that I noticed,
while trying to sort out my own recently commissioned NFS setup,
is that the -r1024 mount flag is *crucial* when the network is
100BaseT and the server is a new, fast amd64 box, and the client
is an old P3-500 with a RealTek ethernet card.  It works fine,
now, but tcpdump showed that it was retrying forever without.
Even NFS over TCP seemed to suffer a bunch of error-related
retries which amounted to stalls in the client.

Is there any way for this sort of thing to be adjusted
automatically?

Cheers,

-- 
Andrew