From owner-freebsd-stable Wed Apr 21 15:59:28 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 47507153C2; Wed, 21 Apr 1999 15:58:00 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from alphard (alphard [128.130.111.37]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id AAA24822; Thu, 22 Apr 1999 00:51:00 +0200 (MET DST) Date: Thu, 22 Apr 1999 00:51:03 +0200 (MET DST) From: Gerald Pfeifer To: Matthew Dillon Cc: Mikhail Teterin , Peter Wemm , current@freebsd.org, stable@freebsd.org Subject: NFSv3 seriously broken in 3.1 In-Reply-To: <199904212009.NAA08036@apollo.backplane.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 I'm only subscribed to freebsd-stable, so I missed the original thread, but reading the lines below, a question arises: On Wed, 21 Apr 1999, Matthew Dillon wrote: > Well, you already see a lot of the pure bug fixes being backported. > What you don't see in -stable are the bug fixes that also depend on the > rewritten portions of the system, nor do you see the rewritten portions > of the system themselves. The latest NFS patch is borderline [...] Are you aware that NFSv3 seems to be seriously broken, at least for FreeBSD 3.1 clients connecting to a Solaris 2.6 server? Has that been fixed for current resp. stable? If not, what can I do to help getting this fixed? Symptoms are the following: We upgraded a perfectly running 2.2.7 client to 3.1, and out of a sudden NFS performed sluggish, sometimes even hanging for ten, twenty seconds, even five minutes or more. Adding the NFSv2 compatibility option to the AMD tables solved the problem. 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