Date: Tue, 20 Jun 2006 21:38:56 +0100 From: Brian Candler <B.Candler@pobox.com> To: obrien@freebsd.org, freebsd-current@freebsd.org Subject: Re: Often experiencing nfs server foo:/bar: not responding Message-ID: <20060620203856.GA6745@uk.tiscali.com> In-Reply-To: <20060620202525.GA45624@dragon.NUXI.org> References: <20060620034229.GA48515@dragon.NUXI.org> <20060620141953.GB5731@uk.tiscali.com> <20060620202525.GA45624@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060620203856.GA6745>