Date: Tue, 15 Feb 2000 16:00:46 -0500 (EST) From: Kenny Drobnack <kdrobnac@mission.mvnc.edu> To: Joe Greco <jgreco@ns.sol.net> Cc: Peter Wemm <peter@netplex.com.au>, hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? Message-ID: <Pine.GSO.3.96.1000215155318.29627D-100000@mission.mvnc.edu> In-Reply-To: <200002151608.KAA54469@aurora.sol.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.96.1000215155318.29627D-100000>