From owner-freebsd-hackers Wed May 24 16:35:01 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA27385 for hackers-outgoing; Wed, 24 May 1995 16:35:01 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA27376 for ; Wed, 24 May 1995 16:34:56 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id QAA27806; Wed, 24 May 1995 16:37:57 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id QAA00144; Wed, 24 May 1995 16:35:01 -0700 Message-Id: <199505242335.QAA00144@corbin.Root.COM> To: jbryant@endersbox.iadfw.net cc: freebsd-hackers@FreeBSD.org Subject: Re: mb_map full In-reply-to: Your message of "Wed, 24 May 95 16:52:30 CDT." <199505242152.QAA13381@server.iadfw.net> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 24 May 1995 16:35:00 -0700 Sender: hackers-owner@FreeBSD.org Precedence: bulk >We are currently having a major problem. > >Our news server is a heavily used machine, is a pentium, has 128M RAM and >128M swap space, and is usually up to 80% swapbound. > >The problem is that the system seems to temporarily freeze for minutes at >a time. Last night I noticed a syslog saying "mb_map full" around the >time of the freeze, did a check, and found a load of those corresponding >roughly with previous freeze-ups. Add options "NMBCLUSTERS=2048" to you kernel config file. There have been so many complaints about this that I'm going to make it dynamic (based on maxusers) RSN. -DG