From owner-freebsd-stable Wed Apr 28 11: 1:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 2F67114E65 for ; Wed, 28 Apr 1999 11:00:37 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from markab (markab [128.130.111.33]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id UAA12313; Wed, 28 Apr 1999 20:00:17 +0200 (MET DST) Date: Wed, 28 Apr 1999 20:00:17 +0200 (MET DST) From: Gerald Pfeifer To: "David O'Brien" Cc: stable@freebsd.org Subject: Re: NFSv3 seriously broken in 3.1 In-Reply-To: <19990423194745.A42940@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Apr 1999, David O'Brien wrote: >> Why I brought this to stable and why think this is rather important is >> the following: >> >> We had a perfectly stable 2.2.7 system which worked fine with our >> Solaris 2.6 server for several months. Merely by upgrading to 3.1 and >> without changing the AMD configuration one bit, the setup broke! > Can you describe the breakage? > > You weren't specifying "nfsv2" in the maps you were using in 2.2.7? Right. We had two identical FreeBSD 2.2.7 clients (PentiumII) and one SunOS 4.1.x Server. No nfsv2/nfsv3 or tcp/upd options were specified in the AMD maps at all. . Originally, both clients were operating without any problems. . We upgraded the server to Solaris 2.6. No problems. . We upgraded one client to FreeBSD 3.1. Out of a sudden, NFS got rather slow and regularily we had NFS access hang for some seconds to a couple of minutes or even more. No problems with the FreeBSD 2.2.7 machine. . I added "nfsv2" to the AMD maps. Suddenly the FreeBSD 3.1 machine was as fast as it was when running 2.2.7. The behavior of the FreeBSD 2.2.7 machine remained as fast as it was. (Please note that our current Ethernet is rather bad and overloaded from a hardware point of view.) > If the list truly feels that v2/UDP should be the default rather than > v3/UDP, I'll glady change it for -STABLE (but not -CURRENT). I want > 3.2 to be the most stable OS we can muster up. Me, too! I strongly suggest making NFSv2/UPD the default for 3.2 (unless the problems with NFSv3 definitely have been fixed, that is). Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message