From owner-freebsd-hackers  Sat Sep  6 10:31:06 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA23337
          for hackers-outgoing; Sat, 6 Sep 1997 10:31:06 -0700 (PDT)
Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA23332
          for <hackers@freebsd.org>; Sat, 6 Sep 1997 10:31:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.6/8.6.12) with SMTP id KAA24492; Sat, 6 Sep 1997 10:25:03 -0700 (PDT)
Message-Id: <199709061725.KAA24492@lestat.nas.nasa.gov>
X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol
To: Josef Karthauser <joe@pavilion.net>
Cc: hackers@freebsd.org
Subject: Re: Boot-Time Memory Allocation Problem?? :-( 
Reply-To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Jason Thorpe <thorpej@nas.nasa.gov>
Date: Sat, 06 Sep 1997 10:25:03 -0700
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 6 Sep 1997 18:16:16 +0100 
 Josef Karthauser <joe@pavilion.net> wrote:

 > Hi guys,
 > I've got a boot time memory allocation problem that I can't track down.
 > Can anyone shed any light on it please?

We ran into this in NetBSD, too.  Basically, you're bumping into resource
limits while fsck'ing the large partition.  What we did was increase the
default limits to something that made sense for modern systems.

 > > > cannot alloc 7179074 bytes for lncntp
 > > > /dev/rccd0a: CAN'T CHECK FILE SYSTEM.
 > > > /dev/rccd0c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                            Home: +1 408 866 1912
NAS: M/S 258-6                                       Work: +1 415 604 0935
Moffett Field, CA 94035                             Pager: +1 415 428 6939