From owner-freebsd-current@FreeBSD.ORG Tue Oct 12 08:46:06 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 1BC1016A4CF for ; Tue, 12 Oct 2004 08:46:06 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB0B143D46 for ; Tue, 12 Oct 2004 08:46:05 +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 i9C8h4pf063752; Tue, 12 Oct 2004 04:43:04 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i9C8gxbx063748; Tue, 12 Oct 2004 04:43:04 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 12 Oct 2004 04:42:59 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Benjamin Lutz In-Reply-To: <200410120011.40517.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: Tue, 12 Oct 2004 08:46:06 -0000 On Tue, 12 Oct 2004, Benjamin Lutz wrote: > > When you're experiencing this problem, can the NFS client ping the NFS > > server? > > Yes. > > > Are other NFS clients able to continue to access the NFS > > server without problems? > > Partially. Other clients can access parts of the exported share. It > appears that as soon as they access the directory in which the first > program froze, they freeze as well. If you log into the server and try to access that directory, do you succeed? You talked about having non-FreeBSD 5.x clients as well, I think, in an earlier e-mail -- if a FreeBSD 5.x client wedges on a directory on the server, will another non-FreeBSD client also wedge on touching the directory? Is it always the same director(y/ies) in which the wedge occurs? The behavior you describe above sounds like it might be a problem with the server, or, that the server generates bad or maybe just different responses that trigger a client bug for particular directories or in particular circumstances? With the exceptions of things like distributed advisory locking (rpc.lockd, etc), bugs in one client won't generally trigger the problem in another client a the same time unless it's a common property of the directory they touch. Ruling out debug.mpsafenet and/or if_re checksum issues would both be useful things to do. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research