Date: Fri, 4 Nov 2005 18:33:29 +0100 From: Thierry Herbelot <thierry@herbelot.com> To: freebsd-current@freebsd.org Cc: Andre Oppermann <andre@freebsd.org> Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 Message-ID: <200511041833.30955.thierry@herbelot.com> In-Reply-To: <20051104163526.GC82727@flame.pc> References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc>
next in thread | previous in thread | raw e-mail | index | archive | help
Le Friday 4 November 2005 17:35, Giorgos Keramidas a écrit : > On 2005-11-04 17:12, Andre Oppermann <andre@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511041833.30955.thierry>