From owner-freebsd-hackers Wed May 12 21:41:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.talcom.net (unknown [209.5.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 81CC114FB8 for ; Wed, 12 May 1999 21:41:15 -0700 (PDT) (envelope-from leo@homer.talcom.net) Received: (from leo@localhost) by homer.talcom.net (8.8.8/8.8.5) id AAA25528 for hackers@freebsd.org; Thu, 13 May 1999 00:43:57 -0400 (EDT) Date: Thu, 13 May 1999 00:43:56 -0400 From: Leo Papandreou To: hackers@freebsd.org Subject: Re: fsck and large file system Message-ID: <19990513004356.A23725@homer.talcom.net> References: <199905121936.MAA87808@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199905121936.MAA87808@apollo.backplane.com>; from Matthew Dillon on Wed, May 12, 1999 at 12:36:24PM -0700 X-No-Archive: Yes X-Organization: Not very, no. X-Wife: Forgotten but not gone. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 12, 1999 at 12:36:24PM -0700, Matthew Dillon 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. > : > :--- > :Jim C., President | C A R R O L L - N E T, Inc. > :201-488-1332 | New Jersey's Premier Internet Service Provider > :www.carroll.com | > : | Want to grow your business and at the same > : | time, decrease costs? Ask about the > :www.message-server.com | Carroll-Net Message Server. > > The traditional rule of thumb for swap is to have 2x the swap as you > have main memory. But in your case, considering the size of the > filesystems you have to deal with, I recommend reserving at least 1GB > of swap for the system. Maybe, but for fsck purposes 2x worked for us. 128M ram, 144G array. Not a problem. Takes a long time of course - real long if you have to fsck a degraded array that's screeching at the top of it's lungs. > > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message