From owner-freebsd-questions  Wed Apr 17 19:28:53 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA05529
          for questions-outgoing; Wed, 17 Apr 1996 19:28:53 -0700 (PDT)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA05521
          for <questions@freebsd.org>; Wed, 17 Apr 1996 19:28:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id TAA06955; Wed, 17 Apr 1996 19:28:42 -0700 (PDT)
Message-Id: <199604180228.TAA06955@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol
To: questions@freebsd.org
cc: mcs@vpm.com
Subject: Re: Help!! What is 'mb_map full' messages mean? 
In-reply-to: Your message of "Wed, 17 Apr 1996 14:12:57 PDT."
             <9604172112.AA14947@a13fs> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Wed, 17 Apr 1996 19:28:42 -0700
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I saw a 'mb_map full' message on the console and don't know what that means.
>  Can anyone enlighten
>me as to what that means?  This all started the other day when I got the
> message:
>
>    "too many files opened"
>
>When I had this condition, I could do anything frmo the command line and I
> attempts to login,
>remotely, failed.  The /usr partition was 108% full and dmesg said I a table
> full.
>
>A rebote of the server didn't necessarily fix this problem.  Now the server
> is behaving
>irratically and I need some help.

   First, your email is really broken and not replyable - the From: address
was not a fully qualified domain name. Second, you really need watch those
line lengths - 95 columns is a bit weird.
   Okay, now to your problem: the mb_map full is caused by there not being
enough mbuf clusters. Try increasing "maxusers" in your kernel config file
to something more appropriate (like say, 64 to start and if that doesn't fix
it, try 100). This might also fix the "too many files" problem, but I'm not
sure where that's coming from, so perhaps not.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project