From owner-freebsd-net Fri Jul 7 13:22:21 2000 Delivered-To: freebsd-net@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id B665D37C322 for ; Fri, 7 Jul 2000 13:22:06 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 77460 invoked by uid 1000); 7 Jul 2000 20:15:21 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jul 2000 20:15:21 -0000 Date: Fri, 7 Jul 2000 15:15:21 -0500 (CDT) From: Mike Silbersack To: "Richard A. Steenbergen" Cc: Bosko Milekic , freebsd-net@FreeBSD.ORG Subject: Re: stuck in LAST_ACK In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Jul 2000, Richard A. Steenbergen wrote: > The full LAST_ACK list was in a previous email, 4.0-STABLE, didn't think > the newreno stuff was an issue there. It's not newreno related, it's a fix that is related to sockets getting stuck in LAST_ACK when the system is low/out of mbufs. (And the patch has been mfc'd to 3 and 4.) How old is your -STABLE? The patch was added on June 8th or so. Although with your huge number of mbufs, I doubt you ran out an caused the situation. OTOH, the high number of mbufs/mbuf clusters you have is almost worrysome; a netkill on that box could eat up a LOT of memory, which won't get freed. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message