Date: Mon, 3 Jul 2006 20:50:09 +1000 From: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> To: Robert Watson <rwatson@FreeBSD.org> 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 Message-ID: <20060703105009.GA89088@duncan.reilly.home> In-Reply-To: <20060703100038.I26325@fledge.watson.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060703105009.GA89088>