From owner-freebsd-questions Sun Dec 6 10:54:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24021 for freebsd-questions-outgoing; Sun, 6 Dec 1998 10:54:44 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from cicero.snikrep.net ([204.157.104.243]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23965 for ; Sun, 6 Dec 1998 10:53:09 -0800 (PST) (envelope-from aron@flyingcroc.com) Received: from chaos.necropolis.org (chaos.necropolis.org [204.157.104.249]) by cicero.snikrep.net (8.8.5/8.8.5) with ESMTP id KAA25490 for ; Sun, 6 Dec 1998 10:52:49 -0800 (PST) Date: Sun, 6 Dec 1998 10:52:47 -0800 (PST) From: aron X-Sender: aron@chaos.necropolis.org To: FreeBSD-questions@FreeBSD.ORG Subject: NMBCLUSTERS: Max Sane Values?? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.0-RELEASE The handbook says max for NMBCLUSTERS is 4096 however I am pretty sure that it is out of date... I currently have NMBCLUSTERS set to 10240 with no ill effects yet i still get panics every two days or so... (the box mostly runs tons of apache procs) so my two curiosities are: is there a max sane value for NMBCLUSTERS and if so what is it ? and why does this situation cause a kernel panic anyway?? I seem to remember a similar situation with NetBSD a while back which cured the kernel panics when mbufs were exhausted and thought freebsd had also corrected the problem even earlier.... any info or pointers appreciated. aron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message