From owner-freebsd-stable@FreeBSD.ORG Fri Feb 26 12:19:10 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37B6D106566B for ; Fri, 26 Feb 2010 12:19:10 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id C5C7A8FC1C for ; Fri, 26 Feb 2010 12:19:09 +0000 (UTC) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 3B954153433; Fri, 26 Feb 2010 13:19:08 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hP93-lGcjAee; Fri, 26 Feb 2010 13:19:06 +0100 (CET) Received: from [192.168.10.67] (opteron [192.168.10.67]) by mail.digiware.nl (Postfix) with ESMTP id 3633E15342F; Fri, 26 Feb 2010 13:19:06 +0100 (CET) Message-ID: <4B87BCAC.2050009@digiware.nl> Date: Fri, 26 Feb 2010 13:21:00 +0100 From: Willem Jan Withagen Organization: Digiware User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: Jeremy Chadwick References: <4B86F384.3010308@digiware.nl> <2a41acea1002251459v40e8c6ddxd0437decbada4594@mail.gmail.com> <4B8795B1.4020006@digiware.nl> <20100226120339.GB17798@icarus.home.lan> In-Reply-To: <20100226120339.GB17798@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, Jack Vogel Subject: Re: em0 freezes on ZFS server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2010 12:19:10 -0000 On 26-2-2010 13:03, Jeremy Chadwick wrote: > On Fri, Feb 26, 2010 at 10:34:41AM +0100, Willem Jan Withagen wrote: >> This is wat netstat -m told me when it refused to revive em0: > > Below are the netstat -m counters/lines of concern: > >> 24980/2087/27067 mbufs in use (current/cache/total) >> 24530/1070/25600/25600 mbuf clusters in use (current/cache/total/max) >> 55305K/2801K/58106K bytes allocated to network (current/cache/total) > > Note how close the "current" value is to that of "total". I'm not too > surprised you're seeing what you are as a result of this. What on earth > is this machine doing at all times? > > Comparatively, here's some of our servers' netstat -m stats. All these > boxes do nightly backups to a centralised box on a private gigE network. > All boxes use em(4). > > RELENG_7 amd64 2010/01/09 -- primary HTTP, pri DNS, SSH server + ZFS > > 514/1931/2445 mbufs in use (current/cache/total) > 512/540/1052/25600 mbuf clusters in use (current/cache/total/max) > 1152K/6394K/7547K bytes allocated to network (current/cache/total) That's why I wrote that I assumed that the mbuf stats where a result of the pipe overflowing when the device went down. (I've seen this discussed in another thread as well) At the moment off em0-freeze, I was running 4 bitbake compile jobs of our software tree. That's a lot of small file access, but like you say nothing really major. --WjW