From owner-freebsd-fs@FreeBSD.ORG Thu Jun 10 11:48:33 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3762C106566B for ; Thu, 10 Jun 2010 11:48:33 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by mx1.freebsd.org (Postfix) with ESMTP id 1E61E8FC19 for ; Thu, 10 Jun 2010 11:48:33 +0000 (UTC) Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta07.emeryville.ca.mail.comcast.net with comcast id UBXx1e0060lTkoCA7BoY5Q; Thu, 10 Jun 2010 11:48:32 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta04.emeryville.ca.mail.comcast.net with comcast id UBoY1e0013S48mS8QBoYXq; Thu, 10 Jun 2010 11:48:32 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 09CE09B418; Thu, 10 Jun 2010 04:48:32 -0700 (PDT) Date: Thu, 10 Jun 2010 04:48:32 -0700 From: Jeremy Chadwick To: Anders Nordby Message-ID: <20100610114831.GB71432@icarus.home.lan> References: <20100608083649.GA77452@fupp.net> <20100609122517.GA16231@fupp.net> <20100610081710.GA64350@server.vk2pj.dyndns.org> <20100610110609.GA87243@fupp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100610110609.GA87243@fupp.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@FreeBSD.org, Peter Jeremy Subject: Re: Odd network issues on ZFS based NFS server X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2010 11:48:33 -0000 On Thu, Jun 10, 2010 at 01:06:09PM +0200, Anders Nordby wrote: > Hi, > > On Thu, Jun 10, 2010 at 06:17:10PM +1000, Peter Jeremy wrote: > > I wonder if your system is running out of free RAM. How would you > > like to monitor "inactive", "cache" and "free" from either "systat -v" > > or "vmstat -s" whilst the problem is occurring. > > > > Does something like > > perl -e '$x = "x" x 10000000;' > > temporarily correct the problem? > > While the problem is happening: > > root@unixfile:~# vmstat -s Can you also provide "vmstat -i" output, both when the issue is happening and after the machine has been rebooted (but been up for 5-10 minutes)? Thanks. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |