From owner-freebsd-current Thu May 27 11:29:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 164DA14BCF for ; Thu, 27 May 1999 11:29:39 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA14859; Thu, 27 May 1999 11:29:28 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 27 May 1999 11:29:27 -0700 (PDT) From: Doug White To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: -Current still leaking mbuf's In-Reply-To: <199905271447.JAA04258@home.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 May 1999, Kevin Day wrote: > I've got two systems that panic about every 48 hours, saying they're out of > mbuf's. I've tried raising maxusers. (It's at 128 now, but i've gone up to > 256 and still seen the same thing). > > I believe it's a leak, since it's pretty consistant how long it will stay up > before it runs out. > > I've tried raising NBMCLUSTERs, but this just seems to prolong it before it > finally panic's. How high do you have it set? You might want to collect some netstat -m stats as time goes on. In addition to being easier to read, it may give you some hints as to how high you want to go with mbuf clusters. You can crank them pretty high if you're on 3.2 or later. > The only unusual thing about these two machines are that they're very heavy > NFS client users. That might do it by itself irrespective of any bugs. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message