From owner-freebsd-hackers Sun May 16 4:49:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.xs4all.nl (smtp2.xs4all.nl [194.109.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 57FFF15389 for ; Sun, 16 May 1999 04:49:15 -0700 (PDT) (envelope-from alexlh@funk.org) Received: (from root@localhost) by smtp2.xs4all.nl (8.8.8/8.8.8) id NAA02360; Sun, 16 May 1999 13:49:14 +0200 (CEST) From: Alex Le Heux To: freebsd-hackers@freebsd.org X-Via: imploder /usr/local/lib/mail/news2mail/news2mail at smtp2.xs4all.nl Subject: Re: fsck and large file system Date: Sun, 16 May 1999 13:48:41 +0000 Organization: XS4ALL Internet BV Message-ID: <373ECCB9.34648FFA@funk.org> In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Carroll wrote: > > I was wondering if anyone has done any work on fsck and very large file > systems. We have a system that has 126 GB RAID Array. As you can imagine, > fsck chokes trying to alloc enough blocks to store it's internal data > structures (128 MB RAM, 128 MB Swap) > > We would like to treat this array as a single large disk, and was wondering > if anyone else had run into this situation, and had a work around. > > Note: I know we could just partition the array to two smaller systems > (which is what we are planning to do if we can't get past this), but I > thought I'd take a shot and see if anyone else had a work around. Maybe I'm completely wrong here, but didn't I read somewhere that with softupdates it would theoretically be possible to boot the system before the fsck and fsck while it's running? Can anyone comment on this? Alex -- +--------------------------------+-------------------+ | SMTP: | E-Gold: 101979 | | ICBM: N52 22.647' E4 51.555' | PGP: 0x1d512a3f | +--------------------------------+-------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message