Date: Thu, 22 Apr 1999 00:51:03 +0200 (MET DST) From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Mikhail Teterin <mi@misha.cisco.com>, Peter Wemm <peter@netplex.com.au>, current@freebsd.org, stable@freebsd.org Subject: NFSv3 seriously broken in 3.1 Message-ID: <Pine.GSO.4.10.9904220043070.22794-100000@alphard.dbai.tuwien.ac.at> In-Reply-To: <199904212009.NAA08036@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.9904220043070.22794-100000>