From owner-freebsd-current@FreeBSD.ORG  Wed Jun 21 00:39:09 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
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 D80FD16A47B;
	Wed, 21 Jun 2006 00:39:09 +0000 (UTC)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
	[128.208.78.105])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8214743D49;
	Wed, 21 Jun 2006 00:39:09 +0000 (GMT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
	[127.0.0.1])
	by troutmask.apl.washington.edu (8.13.7/8.13.7) with ESMTP id
	k5L0cT0V099587; Tue, 20 Jun 2006 17:38:29 -0700 (PDT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.13.7/8.13.7/Submit) id
	k5L0cSam099586; Tue, 20 Jun 2006 17:38:28 -0700 (PDT)
	(envelope-from sgk)
Date: Tue, 20 Jun 2006 17:38:28 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Chuck Lever <chucklever@gmail.com>
Message-ID: <20060621003828.GC99008@troutmask.apl.washington.edu>
References: <20060620205617.GR83482@over-yonder.net>
	<20060620223115.21443.qmail@web30803.mail.mud.yahoo.com>
	<20060620225118.GA98667@troutmask.apl.washington.edu>
	<76bd70e30606201723k1b561970ra8f7b516c89acbca@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <76bd70e30606201723k1b561970ra8f7b516c89acbca@mail.gmail.com>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-current@freebsd.org, Robert Watson <rwatson@freebsd.org>,
	Mohan Srinivasan <mohan_srinivasan@yahoo.com>,
	"Matthew D. Fuller" <fullermd@over-yonder.net>
Subject: Re: Often experiencing nfs server foo:/bar: not responding
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jun 2006 00:39:09 -0000

On Tue, Jun 20, 2006 at 05:23:38PM -0700, Chuck Lever wrote:
> On 6/20/06, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
> >
> >I've seen the problem described by David on RELENG_6.
> >
> >You can see the network topology at
> >http://troutmask.apl.washington.edu/~kargl/hpc.html
> >The NFS server is on node10 (bge1) and /home is exported to node11
> >through node15.  If I mount node10:/usr/src on node15 a "make installworld"
> >will result in a never ending stream of "server not responding messages".
> 
> Has anyone who has seen this issue tried using the dumb timer mount option?
> 

I did not try that option in that the description suggested to
me that -d is applicable to slow networks.  Before I tried
-d, I decided to see what happens.

Interesting.

node11:kargl[214] rsync -av kargl@node10:prj /tmp
...
sent 11970 bytes  received 34071110 bytes  22722053.33 bytes/sec
total size is 34032098  speedup is 1.00
node11:kargl[215] rm -rf /tmp/prj
node11:kargl[216] time cp -R ~/prj /tmp
nfs server master:/home: not responding
nfs server master:/home: not responding
nfs server master:/home: not responding

/tmp is a memory filesystem and /home/kargl is NFS exported.


-- 
Steve