From owner-freebsd-current Thu May 27 7:47:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 500E51530C for ; Thu, 27 May 1999 07:47:33 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id JAA04258 for current@freebsd.org; Thu, 27 May 1999 09:47:28 -0500 (CDT) From: Kevin Day Message-Id: <199905271447.JAA04258@home.dragondata.com> Subject: -Current still leaking mbuf's To: current@freebsd.org Date: Thu, 27 May 1999 09:47:27 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. The only unusual thing about these two machines are that they're very heavy NFS client users. Is there anything any of you would like to see, if someone's willing to try to debug this? vmstat -m doesn't show anything too out of the ordinary, but I've got several coredumps waiting. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message