From owner-freebsd-hackers Fri May 14 5:44:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 6FE6614E77 for ; Fri, 14 May 1999 05:44:43 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id OAA42788; Fri, 14 May 1999 14:44:35 +0200 (CEST) (envelope-from des) To: mtaylor@cybernet.com Cc: Matthew Jacob , freebsd-hackers@FreeBSD.ORG, Jim Carroll Subject: Re: fsck and large file system References: From: Dag-Erling Smorgrav Date: 14 May 1999 14:44:35 +0200 In-Reply-To: "Mark J. Taylor"'s message of "Wed, 12 May 1999 15:18:22 -0400 (EDT)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Mark J. Taylor" writes: > The problem that we ran into in a system with several 130 MB RAID5 arrays > is that the fsck was running out of RAM+swap. We had to add a vnode to swap > to before the fsck would complete (basically added more swap space). > We had to have over 100 MB swap space to fsck the 130 MB volume, and the > system has 64 MB RAM. This was is 2.2.8 (haven't upgraded it yet). I *really* hope you meant 130 GB and not 130 MB :) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message