From owner-freebsd-current@FreeBSD.ORG Mon Oct 11 21:48:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43C0616A4F1 for ; Mon, 11 Oct 2004 21:48:30 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB67E43D1D for ; Mon, 11 Oct 2004 21:48:29 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id i9BLksQV055907; Mon, 11 Oct 2004 17:46:54 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i9BLkrRr055904; Mon, 11 Oct 2004 17:46:54 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 11 Oct 2004 17:46:53 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Benjamin Lutz In-Reply-To: <200410111840.40750.benlutz@datacomm.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: NFS trouble X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2004 21:48:30 -0000 On Mon, 11 Oct 2004, Benjamin Lutz wrote: ... > Nothing gets logged on the server, the client logs this repeatedly: > nfs server uno:/var/www/localhost: not responding > > Forcibly unmounting the share works and seems to unfreeze the frozen > applications. > > This behaviour is new. I cannot say when exactly I've first seen this, > but I think it must have appeared somewhere between BETA5 and BETA7. > > What can I do to make NFS work more reliably again? When you're experiencing this problem, can the NFS client ping the NFS server? Are other NFS clients able to continue to access the NFS server without problems? It might be interesting to use tcpdump to see if the client stops sending RPCs or not, and if not, whether the server responds to them. If you set debug.mpsafenet=0 in loader.conf, does the problem go away? Also, finally, what ethernet device(s) are you using, and are there any notes about those devices in the dmesg output? Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research