From owner-freebsd-hackers  Wed Apr 21  9:34: 9 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from home.dragondata.com (home.dragondata.com [204.137.237.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9CA5114C3E; Wed, 21 Apr 1999 09:34:06 -0700 (PDT)
	(envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.9.2/8.9.2) id LAA29863;
	Wed, 21 Apr 1999 11:31:05 -0500 (CDT)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199904211631.LAA29863@home.dragondata.com>
Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need tester
In-Reply-To: <Pine.BSF.3.96.990421101558.11384i-100000@cygnus.rush.net> from Alfred Perlstein at "Apr 21, 1999 10:32:19 am"
To: bright@rush.net (Alfred Perlstein)
Date: Wed, 21 Apr 1999 11:31:05 -0500 (CDT)
Cc: dillon@apollo.backplane.com, rb@gid.co.uk, wilko@yedi.iaf.nl,
	current@FreeBSD.ORG, hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> yeah the clocks are not setup properly :) but otherwise i'm just
> gonna say HOLY SH*T you fixed NFS! :)


We all owe Matt big for this. :)


> I'm using the default mount operations, as far as NFS server
> not responding messages, i have no clue, but the server is still
> up and i've seen that message happen when a lot of pressure is
> being put on an NFS server even though everything is fine.

Try mounting with -d... Can I make a guess that the NFS mount is going over
100MB ethernet? I have a strong theory that the dynamic retransmit timer
needs rework for low latency connections, with high variability in their
performance during high traffic. (lots of collisions)


Kevin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message