Date: Wed, 06 Mar 2002 23:02:26 +0000 From: Ian Dowse <iedowse@maths.tcd.ie> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: "Jan L. Peterson" <jlp@softhome.net>, freebsd-stable@FreeBSD.ORG Subject: Re: crashes on 4.5-RELEASE Message-ID: <200203062302.aa66019@salmon.maths.tcd.ie> In-Reply-To: Your message of "Wed, 06 Mar 2002 14:51:22 PST." <200203062251.g26MpM258927@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200203062251.g26MpM258927@apollo.backplane.com>, Matthew Dillon wri tes: > > I wonder if a TCP nfs mount would cause the problem to occur more > often. Then you wouldn't need an IPFW rule.... a simple TCP stall > in a heavily loaded environment would be enough to cause the output > buffer to grow to a considerable size. Yes, that's certainly possible. Can someone who has a crash dump handy run netstat -m -N kernel.X -M vmcore.X to get the mbuf stats? I think with TCP the buildup would be much slower, as a (as far as I remember) retransmits are limited. In -CURRENT (which is the only place I have seen the IPFW/NFS mbuf exhaustion) I think sosend() was returning EPERM, but the mbufs were still building up. That may be a new bug somewhere. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi? <200203062302.aa66019>