From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 17:33:43 2005 Return-Path: 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 6002B16A41F; Fri, 4 Nov 2005 17:33:43 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 752CB43D53; Fri, 4 Nov 2005 17:33:42 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp3-g19.free.fr (Postfix) with ESMTP id B1BD33752F; Fri, 4 Nov 2005 18:33:41 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jA4HXbQ7007369; Fri, 4 Nov 2005 18:33:40 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Fri, 4 Nov 2005 18:33:29 +0100 User-Agent: KMail/1.8.2 References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> In-Reply-To: <20051104163526.GC82727@flame.pc> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200511041833.30955.thierry@herbelot.com> Cc: Andre Oppermann Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 17:33:43 -0000 Le Friday 4 November 2005 17:35, Giorgos Keramidas a écrit : > On 2005-11-04 17:12, Andre Oppermann wrote: > > Ok, thanks to Danny Braniss and Peter Holm the KASSERT is working now. > > Very fast fix. Thanks. I barely had the time to build a kernel and > read Peter's warning about a broken build, before the fix was ready :) > Hello, I have applied your second patch, to solve an mbuf exhaustion which I see with NFS traffic. I still have the same symptoms : after launching over an ssh session a recusrive 'ls' over an NFS disk, the -current NFS client is blocked (and complains with 'nfs server truc:/files: not responding') - I first saw this when cvs-ing the sources from the same shared disk. I have enclosed the trace showing the mbuf stats : multi-cur% while (1) while? sleep 10 while? netstat -m | head -2 while? end 65/460/525 mbufs in use (current/cache/total) 64/210/274/3776 mbuf clusters in use (current/cache/total/max) 66/2124/2190 mbufs in use (current/cache/total) 64/2016/2080/3776 mbuf clusters in use (current/cache/total/max) 68/3652/3720 mbufs in use (current/cache/total) 65/3439/3504/3776 mbuf clusters in use (current/cache/total/max) 67/3908/3975 mbufs in use (current/cache/total) 64/3712/3776/3776 mbuf clusters in use (current/cache/total/max) 67/3908/3975 mbufs in use (current/cache/total) 64/3712/3776/3776 mbuf clusters in use (current/cache/total/max) This isssue is seen on 3 different PCs running recent -current, clients for a FreeBSD-6 NFS server (same problem when the NFS server is NetBSD). All 3 clients have a small RAM, which may be a cause for faster apparition of the issue. TfH