From owner-freebsd-current@FreeBSD.ORG Sun Feb 1 22:53:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFDC516A4CE for ; Sun, 1 Feb 2004 22:53:00 -0800 (PST) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id D36D143D41 for ; Sun, 1 Feb 2004 22:52:55 -0800 (PST) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i126q9e3028592; Mon, 2 Feb 2004 17:52:10 +1100 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost)i126q2YS028591; Mon, 2 Feb 2004 17:52:02 +1100 (EST) (envelope-from jeremyp) Date: Mon, 2 Feb 2004 17:52:02 +1100 From: Peter Jeremy To: Oliver Brandmueller Message-ID: <20040202065202.GQ908@cirb503493.alcatel.com.au> References: <20040130115025.GB96881@e-Gitt.NET> <200401310143.51186.freebsd-current@webteckies.org> <20040131114548.GA2632@e-Gitt.NET> <20040131130337.GH774@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040131130337.GH774@cicely12.cicely.de> User-Agent: Mutt/1.4.1i cc: ticso@cicely.de cc: current@freebsd.org Subject: Re: max blockdevice/filesystem size? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 06:53:01 -0000 On Sat, Jan 31, 2004 at 02:03:38PM +0100, Bernd Walter wrote: >One point for a 10T UFS2 filesystem is a limit of 2G inodes. It shouldn't - ino_t is unsigned. >Someone mentioned a problem in another thread with more inodes. It's not clear that his problem was definitely caused by having more than 2G inodes - though it is possible. >Another point is the fsck memory footprint when checking such a >filesystem - that should very much depend on your newfs args and >number of files. Not to mention the disk space eaten by the inodes and time to actually perform an fsck. >Otherwise it should just work. It's probably a good idea to adjust the blocksize, fragsize, cylinders per group and bytes per inode to suit the expected number of files. A larger blocksize (up to a certain point) will improve I/O performance and increase the maximum cylinder size. Fewer cylinders and fewer inodes will speed up fsck. Peter