From owner-freebsd-hackers Wed May 12 11:15:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DC11815A65 for ; Wed, 12 May 1999 11:15:30 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA23752; Wed, 12 May 1999 11:15:14 -0700 Date: Wed, 12 May 1999 11:15:14 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jim Carroll Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fsck and large file system In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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) Huh- I remember fixing this for NetBSD. You have to do a setrlimit within fsck so it can malloc enough space and have enough swap to back that. We were fsck'ing 600GB+ filesystems. > > > 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. > I've been doing 120GB+ filesystems for FreeBSD for quite some time. The real fun will be the 1TB filesystems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message