From owner-freebsd-hackers Wed May 12 12:17:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id E2FFC14BE1 for ; Wed, 12 May 1999 12:17:44 -0700 (PDT) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id PAA23534; Wed, 12 May 1999 15:17:07 -0400 (EDT) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 12 May 1999 15:18:22 -0400 (EDT) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: Matthew Jacob Subject: Re: fsck and large file system Cc: freebsd-hackers@FreeBSD.ORG, Jim Carroll Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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). BTW: this system is getting VERY poor I/O performance, using the DPT SCSI RAID controller and three arrays of four 49 GB Seagate drives. "iozone" reports 340,000 bytes/sec write and 9,800,000 bytes/sec read. This horrendous write rate makes the system virtually unusable. Anyone have any ideas on improving the performance? Would an upgrade from its 2.2.8 to 3.{1,2} help? It is a Pentium 166. During the "iozone" test, there seems to be only a few (less than 10) interrupts from the DPT card per second ("systat -vm 1"). Am I losing interrupts (it would seem so)... ? -Mark Taylor NetMAX Developer mtaylor@cybernet.com On 12-May-99 Matthew Jacob 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) > > 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 --- Mark J. Taylor Networking Research Cybernet Systems mtaylor@cybernet.com 727 Airport Blvd. PHONE (734) 668-2567 Ann Arbor, MI 48108 FAX (734) 668-8780 http://www.cybernet.com/ http://www.netmax.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message