From owner-freebsd-stable@FreeBSD.ORG Wed Feb 27 19:53:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C541F106566C for ; Wed, 27 Feb 2008 19:53:02 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id AE49C8FC17 for ; Wed, 27 Feb 2008 19:53:02 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.13.7) with ESMTP id m1RJr18g092611; Wed, 27 Feb 2008 11:53:01 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id m1RJr1Xu092608; Wed, 27 Feb 2008 11:53:01 -0800 (PST) Date: Wed, 27 Feb 2008 11:53:01 -0800 (PST) From: Matthew Dillon Message-Id: <200802271953.m1RJr1Xu092608@apollo.backplane.com> To: freebsd-stable@freebsd.org, om-lists-bsd@omx.ch References: <200802271845.m1RIjl1O017191@lurza.secnetix.de> Cc: Subject: Re: fsck_ufs: cannot alloc 94208 bytes for inoinfo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 19:53:02 -0000 fsck's memory usage is directly related to the number of inodes and the number of directories in the filesystem. Directories are particularly memory intensive. I've found on my backup system that a UFS1 filesystem with 40 million inodes is about the limit that can be fsck'd (at least with a 32 bit architecture). My cron jobs keep my backup partition below that point. Even in a 64 bit environment you will be limited by swap and the sheer time it takes for fsck to run. It takes well over 8 hours for my backup system to fsck. You can also reduce fsck time by reducing the number of cylinder groups on the disk. I usually max them out (-c 999 and newfs then sets it to the maximum, usually in the 50-80 range). This will improve performance but not reduce the memory required. -Matt