From owner-freebsd-hackers Mon May 22 10:24:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8EC1337BBD9 for ; Mon, 22 May 2000 10:24:29 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA61109; Mon, 22 May 2000 10:24:28 -0700 (PDT) (envelope-from dillon) Date: Mon, 22 May 2000 10:24:28 -0700 (PDT) From: Matthew Dillon Message-Id: <200005221724.KAA61109@apollo.backplane.com> To: Doug Barton Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS server problems on 3.4-S, any interest? References: <39296B54.92935A8B@gorean.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I have two machines at home, one running 3.4-Stable which is my :firewall/natd/file server machine. The other is running 5.0-Current :(around 5/8 right now) which mounts a whole bunch of stuff via amd from :the 3.4 machine. Up until say... 2 months ago, this worked really well. :I never had any nfs performance problems. One of the things I mount for :example is /usr/src, and my make world time didn't suffer much, if at :all. : : However, at some point about 2 months ago (I wish I had a more definite :time period, but the problem has kind of snuck up on me) I have been :getting increasingly bad performance from the nfs mount. I get "nfs :... :Doug First, make sure the 5.x machine is up to date. Second, start looking for network problems, because if you are getting 'host not responding' errors it's probably due to packet loss somewhere. NFS is particularly sensitive to packet loss. This doesn't sound like an NFS problem on the face of it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message