From owner-freebsd-hackers Tue Feb 15 14: 2:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mission.mvnc.edu (mission.mvnc.edu [149.143.2.3]) by builder.freebsd.org (Postfix) with ESMTP id B92F34ACC for ; Tue, 15 Feb 2000 13:04:44 -0800 (PST) Received: from localhost (kdrobnac@localhost) by mission.mvnc.edu (8.9.0/8.9.0) with SMTP id QAA22662; Tue, 15 Feb 2000 16:00:46 -0500 (EST) Date: Tue, 15 Feb 2000 16:00:46 -0500 (EST) From: Kenny Drobnack To: Joe Greco Cc: Peter Wemm , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? In-Reply-To: <200002151608.KAA54469@aurora.sol.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The trick to fsck is that you don't want more inodes than you really need. > Once you get past that, fsck flies. The previous generation of binaries > server, worked on 27 36GB drives split into 10 partitions, designed for > parallelism. Hit RESET and the news filesystems take ~30 seconds to fsck. > > Thanks for the info, I was mostly just curious. I haven't looked much into fsck, so I have no idea how this is accomplished? Is this a modified copy of fsck that only checks inodes marked as used, or is there some other method for doing this (besides a journaling fs that is :-) Also, it seems like 64 bit processors will be in use before 1 TB filesystems are common. Won't the filesystem need to be 64-bitted for that? ----- In computer terms, hardware is the stuff you can hit with a baseball bat, and software is the stuff you can only swear at. -from a web page explaining what hardware, software, and firmware are ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message