From owner-freebsd-bugs@FreeBSD.ORG Fri Nov 27 18:28:47 2009 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E011E106566C for ; Fri, 27 Nov 2009 18:28:47 +0000 (UTC) (envelope-from jhickey@ISI.EDU) Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by mx1.freebsd.org (Postfix) with ESMTP id C2B8A8FC1D for ; Fri, 27 Nov 2009 18:28:47 +0000 (UTC) Received: from pod.isi.edu (pod.isi.edu [128.9.168.186]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id nARISI8k017544; Fri, 27 Nov 2009 10:28:20 -0800 (PST) Received: from pod.isi.edu (localhost.localdomain [127.0.0.1]) by pod.isi.edu (Postfix) with ESMTP id 3ED0316450E; Fri, 27 Nov 2009 10:31:02 -0800 (PST) Received: (from jhickey@localhost) by pod.isi.edu (8.14.3/8.14.3/Submit) id nARIV2Y3001549; Fri, 27 Nov 2009 10:31:02 -0800 Date: Fri, 27 Nov 2009 10:31:02 -0800 From: John Hickey To: "Bjoern A. Zeeb" Message-ID: <20091127183101.GC29107@pod.isi.edu> References: <20091123213609.GD19973@pod.isi.edu> <20091126160522.T37440@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091126160522.T37440@maildrop.int.zabbadoz.net> User-Agent: Mutt/1.5.18 (2008-05-17) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: jhickey@pod.isi.edu Cc: freebsd-bugs@FreeBSD.org, John Hickey Subject: Re: debugging a mbuf leak X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Hickey List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2009 18:28:48 -0000 Thanks for the reply. We managed to track down the leak and have submitted a PR (kern/140853) for it. Thanks, John On Thu, Nov 26, 2009 at 04:07:26PM +0000, Bjoern A. Zeeb wrote: > On Mon, 23 Nov 2009, John Hickey wrote: > > Hi John, > >> One of our main servers here has a slow mbuf leak. We are not sure what >> is causing it at this point. Does anyone have some pointers on how to >> dig further into this? > > There are a couple of things to check: > 1) is it really a leak? > > This can easily be tested by going down to single user and see > if the mbufs got freed again. > > 2) maybe starting with this first: which version of freebsd is this? > > >> Mon Nov 23 13:19:15 PST 2009 >> >> 16364/2836/19200 mbufs in use (current/cache/total) >> 928/2216/3144/132096 mbuf clusters in use (current/cache/total/max) >> 512/1664 mbuf+clusters out of packet secondary zone in use >> (current/cache) >> 0/135/135/66048 4k (page size) jumbo clusters in use >> (current/cache/total/max) >> 0/0/0/33024 9k jumbo clusters in use (current/cache/total/max) >> 0/0/0/16512 16k jumbo clusters in use (current/cache/total/max) >> 5947K/5681K/11628K bytes allocated to network (current/cache/total) >> 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) >> 0/0/0 requests for jumbo clusters denied (4k/9k/16k) >> 0/5/33280 sfbufs in use (current/peak/max) >> 0 requests for sfbufs denied >> 0 requests for sfbufs delayed >> 0 requests for I/O initiated by sendfile >> 0 calls to protocol drain routines >> >> Mon Nov 23 13:24:21 PST 2009 >> >> 18085/2660/20745 mbufs in use (current/cache/total) >> 923/2455/3378/132096 mbuf clusters in use (current/cache/total/max) >> 512/1664 mbuf+clusters out of packet secondary zone in use >> (current/cache) >> 0/135/135/66048 4k (page size) jumbo clusters in use >> (current/cache/total/max) >> 0/0/0/33024 9k jumbo clusters in use (current/cache/total/max) >> 0/0/0/16512 16k jumbo clusters in use (current/cache/total/max) >> 6367K/6115K/12482K bytes allocated to network (current/cache/total) >> 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) >> 0/0/0 requests for jumbo clusters denied (4k/9k/16k) >> 0/5/33280 sfbufs in use (current/peak/max) >> 0 requests for sfbufs denied >> 0 requests for sfbufs delayed >> 0 requests for I/O initiated by sendfile >> 0 calls to protocol drain routines >> >> _______________________________________________ >> freebsd-bugs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-bugs >> To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org" >> > > -- > Bjoern A. Zeeb It will not break if you know what you are doing.