From owner-freebsd-hackers Thu Jul 22 23:42:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 695C814F8F for ; Thu, 22 Jul 1999 23:42:50 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id XAA21217; Thu, 22 Jul 1999 23:42:04 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37980EBC.C38668E1@gorean.org> Date: Thu, 22 Jul 1999 23:42:04 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "David E. Cross" Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf leakage in NFSv3 writes, possbile? References: <199907222246.SAA81283@cs.rpi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: > > Well, I just -STABLED the server to see if it fixed it, but I was certainly > running out. the server had only 3000-ish mbuf chains, and it would go through > them all in a day. Well, have you tried increasing the number of available mbufs and see if you reach a point of stability? Assuming you have enough physical ram you could do 15k mbufs on -Stable without a problem. Check LINT for the nmbclusters option if you need help with it. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message