From owner-freebsd-questions  Sun Aug 27 16:48:21 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id QAA11392
          for questions-outgoing; Sun, 27 Aug 1995 16:48:21 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id QAA11386
          ; Sun, 27 Aug 1995 16:48:19 -0700
Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.11/8.6.5) with ESMTP id QAA00961; Sun, 27 Aug 1995 16:47:07 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id QAA17588; Sun, 27 Aug 1995 16:49:08 -0700
Message-Id: <199508272349.QAA17588@corbin.Root.COM>
To: count@key.hole.fi
cc: jkh@freebsd.org, questions@freebsd.org
Subject: Re: mb_map full ? 
In-reply-to: Your message of "Sun, 27 Aug 95 10:05:51 +0300."
             <199508270705.KAA00394@snafu.muncca.fi> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sun, 27 Aug 1995 16:49:07 -0700
Sender: questions-owner@freebsd.org
Precedence: bulk

>	As I might've mentioned to you, I recently updated snafu.muncca.fi
>	from FreeBSD 1.1 to FreeBSD 2.0.5. Now I've had my first crash :(
>
>	The cause is mb_map full error from kernel, and I do remember reading
>	about it from somewhere but I can't remember how to fix it! And the
>	mailing list archives aren't available...
...
>Aug 27 01:48:18 snafu login: login from noyfb as speedy
>Aug 27 05:54:20 snafu /kernel: mb_map full
>Aug 27 09:52:17 snafu /kernel: FreeBSD 2.0.5-RELEASE #2: Fri Aug 25 19:37:30 EET DST 1995
>Aug 27 09:52:18 snafu /kernel:     count@pc4.muncca.fi:/usr/src/sys/compile/SNAFU
>Aug 27 09:52:18 snafu /kernel: CPU: i486DX (486-class CPU)

   Did the machine hang or something? There is a 4 hour delay between the
mb_map full message and the reboot. 'mb_map full' shouldn't cause the machine
to crash, although it can cause the network to go dead for awhile. To increase
the mb_map add:

options "NMBCLUSTERS=2048"

to your kernel config file. With maxuser at 40, you currently have configured
a limit of about 1150 mbuf clusters...and this isn't enough in your case.

-DG