From owner-freebsd-questions Tue Jul 15 13:05:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA21238 for questions-outgoing; Tue, 15 Jul 1997 13:05:55 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA21226 for ; Tue, 15 Jul 1997 13:05:47 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA20088; Tue, 15 Jul 1997 13:06:07 -0700 (PDT) Message-Id: <199707152006.NAA20088@implode.root.com> To: andrew@ugh.net.au cc: questions@FreeBSD.ORG Subject: Re: NFS connections hanging - more info In-reply-to: Your message of "Wed, 16 Jul 1997 05:16:38 +1000." From: David Greenman Reply-To: dg@root.com Date: Tue, 15 Jul 1997 13:06:06 -0700 Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >The connection will sometimes return again with the messages server has >stop responding, server is alive again. It will be OK for a bit then >dissappear again. > >The STABLE box has a Digital PCI Ethernet Card (de driver), the RELEASE >box has an ISA NE2000 clone (ed driver). What happens when you increase the NFS timeout? I've noticed that the timeout is calculated a bit low and heavy disk activity on the server can sometimes cause the "not responding" messages to come out, even when there isn't a real problem. I think the default timeout value that is calculated in the kernel is actually bogusly low in some versions of FreeBSD, but I could be wrong about that. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project