From owner-freebsd-stable Thu Apr 22 8:34:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A44C314D95; Thu, 22 Apr 1999 08:34:09 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10aLQ8-0007kH-00; Thu, 22 Apr 1999 17:29:44 +0200 From: Sheldon Hearn To: Gerald Pfeifer Cc: Matthew Dillon , Mikhail Teterin , Peter Wemm , current@freebsd.org, stable@freebsd.org Subject: Re: NFSv3 seriously broken in 3.1 In-reply-to: Your message of "Thu, 22 Apr 1999 00:51:03 +0200." Date: Thu, 22 Apr 1999 17:29:44 +0200 Message-ID: <29776.924794984@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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-stable" in the body of the message