From owner-freebsd-questions Wed Nov 5 11:06:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29558 for questions-outgoing; Wed, 5 Nov 1997 11:06:15 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA29550 for ; Wed, 5 Nov 1997 11:06:06 -0800 (PST) (envelope-from mdtancsa@sentex.net) Received: (from mdtancsa@localhost) by granite.sentex.net (8.8.6/8.6.9) id OAA19353 for questions@freebsd.org; Wed, 5 Nov 1997 14:16:48 -0500 (EST) From: Mike D Tancsa Message-Id: <199711051916.OAA19353@granite.sentex.net> Subject: Cant allocate memory for fsck on bootup To: questions@freebsd.org Date: Wed, 5 Nov 1997 14:16:45 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk P133, FreeBSD 2.2-RELENG cvsup'd Nov 3. 128M ram, AHC 2940. It was running a 2.2 snapshot from August or so. Now when I boot, the boot dies with a message something similar to 'cant malloc stat' just before doing an fsck on a 4gig SCSI drive. When I run fsck manually, the drive comes up clean with no errors or warnings. But when I reboot, the same problem comes up. Again, I run fsck, no errors, and type exit, the bootup process continues without problem. Any idea what the problem might be ? The drive that has the problem is the over.view drive for our news server, but there is nothing special about it... I have other 4gig drives on the same controller, and they dont exhibit this problem. In my kernel config, I have it set for 96 users ---Mike