From owner-freebsd-isp  Tue Oct 15 10:02:42 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA20364
          for isp-outgoing; Tue, 15 Oct 1996 10:02:42 -0700 (PDT)
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA20094
          for <freebsd-isp@freebsd.org>; Tue, 15 Oct 1996 09:59:31 -0700 (PDT)
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA26097; Tue, 15 Oct 1996 11:58:12 -0500
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199610151658.LAA26097@brasil.moneng.mei.com>
Subject: Re: **ccd, disk striping, and fsck problems**
To: msv@arisia.net (Mark S. Velasquez)
Date: Tue, 15 Oct 1996 11:58:11 -0500 (CDT)
Cc: freebsd-isp@freebsd.org
In-Reply-To: <2.2.32.19961015153135.0088e40c@207.100.94.5> from "Mark S. Velasquez" at Oct 15, 96 11:31:35 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>  We're running FreeBSD 2.1.5 and I recently striped 3 disks(Quantum 4.3GB,
> 7400 rpm) into one logical volume, and have beeen using it without incident.
> However, when I brought the system down for maintainance, it was unable to
> boot due to an fsck problem(complains about "out of memory"). The filesystem
> was built with "-i 1024", which I feel was appropriate for a filesystem to
> be used as a news server's spool directory, but I'm wondering if this is
> what's causing the problem.
> 
>   Any help is appreciated.

I assume you have a fair amount of physical RAM if you are running a news
server.  That is probably not the problem.

If you are crashing in the "fsck -p" in /etc/rc, I would probably try:

csh -c "unlimit; exec fsck -p"

as a way to circumvent the per process memory limit that you may be
running into.  You can probably stick that right into /etc/rc in place
of the current fsck -p.

... JG