Date: Thu, 22 Apr 1999 17:29:44 +0200 From: Sheldon Hearn <sheldonh@iafrica.com> To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> Cc: Matthew Dillon <dillon@apollo.backplane.com>, Mikhail Teterin <mi@misha.cisco.com>, Peter Wemm <peter@netplex.com.au>, current@freebsd.org, stable@freebsd.org Subject: Re: NFSv3 seriously broken in 3.1 Message-ID: <29776.924794984@axl.noc.iafrica.com> In-Reply-To: Your message of "Thu, 22 Apr 1999 00:51:03 %2B0200." <Pine.GSO.4.10.9904220043070.22794-100000@alphard.dbai.tuwien.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 22 Apr 1999 00:51:03 +0200, Gerald Pfeifer wrote: > 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. CURRENT has been giving me similar problems that weren't (as) obvious in 2.2-STABLE . I've found two client-side work-arounds to improve the situation: 1) Use ``opts:=vers=2,soft,intr'' in /etc/amd.map (see the AMD info page for more details). 2) Don't use AMD. Use direct mounts out of /etc/fstab, eg: src.noc:/a/ncvs /home/ncvs nfs soft,intr 0 0 This causes an apparent hang during FreeBSD boot if the server is unavailable (eg: network fault). Otherwise, all I can suggest is patience. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?29776.924794984>