From owner-freebsd-current@FreeBSD.ORG  Tue Jun 20 20:39:00 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 D1CE016A474;
	Tue, 20 Jun 2006 20:39:00 +0000 (UTC)
	(envelope-from b.candler@pobox.com)
Received: from proof.pobox.com (proof.pobox.com [207.106.133.28])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7020443D72;
	Tue, 20 Jun 2006 20:39:00 +0000 (GMT)
	(envelope-from b.candler@pobox.com)
Received: from proof (localhost [127.0.0.1])
	by proof.pobox.com (Postfix) with ESMTP id 8894E28CAD;
	Tue, 20 Jun 2006 16:38:59 -0400 (EDT)
Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com
	[212.74.113.67])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by proof.sasl.smtp.pobox.com (Postfix) with ESMTP id 5391E59B66;
	Tue, 20 Jun 2006 16:38:58 -0400 (EDT)
Received: from brian by mappit.local.linnet.org with local (Exim 4.61
	(FreeBSD)) (envelope-from <b.candler@pobox.com>)
	id 1Fsmzw-0001l1-Rt; Tue, 20 Jun 2006 21:38:57 +0100
Date: Tue, 20 Jun 2006 21:38:56 +0100
From: Brian Candler <B.Candler@pobox.com>
To: obrien@freebsd.org, freebsd-current@freebsd.org
Message-ID: <20060620203856.GA6745@uk.tiscali.com>
References: <20060620034229.GA48515@dragon.NUXI.org>
	<20060620141953.GB5731@uk.tiscali.com>
	<20060620202525.GA45624@dragon.NUXI.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060620202525.GA45624@dragon.NUXI.org>
User-Agent: Mutt/1.4.2.1i
Cc: 
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: Tue, 20 Jun 2006 20:39:00 -0000

On Tue, Jun 20, 2006 at 01:25:25PM -0700, David O'Brien wrote:
> > # ping -c100 -s1472 your.nfs.server
> > 
> > Run this when the machine is idle; and run it while you are exercising
> > the NFS server. Do you see any packet loss?
> 
> When experiencing "kernel: nfs server server:/files: not responding", I
> ran this suggest ping.  The results were:
> 
>     --- 192.168.1.1 ping statistics ---
>     100 packets transmitted, 100 packets received, 0% packet loss
>     round-trip min/avg/max/stddev = 0.389/0.511/0.767/0.062 ms

OK, thanks. That's a rough and ready test for duplex mismatches and general
network flakiness, so I'd say it's more likely you have an NFS issue.

Regards,

Brian.