From owner-freebsd-hackers Sat Jan 9 21:59:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04675 for freebsd-hackers-outgoing; Sat, 9 Jan 1999 21:59:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04670 for ; Sat, 9 Jan 1999 21:59:34 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA80951; Sat, 9 Jan 1999 21:59:01 -0800 (PST) (envelope-from dillon) Date: Sat, 9 Jan 1999 21:59:01 -0800 (PST) From: Matthew Dillon Message-Id: <199901100559.VAA80951@apollo.backplane.com> To: "Michael G." Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Re: FreeBSD Cluster Size Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm building a chart that describes the different file :formats and how the cluster size is dependent on the :partition size (except ofcourse for HPFS). What I need to :know is what is the cluster size for the FreeBSD :3.0-RELEASE? : :If you know..please do tell : :Thanks. : :Michael G. There is nothing specific to FreeBSD 2.x or 3.x that changes the layout of typical filesystem types. For UFS/FFS, you can mess around with the parameters to newfs to get pretty much whatever layout you want. UFS/FFS puts restrictions on various parameters, but they tend to be relative restrictions, so you can scale the parameters as you like. See 'man newfs' and 'man tunefs'. Also, after 3.0 release, the reallocblks code was fixed and reenabled in UFS/FFS so, effectively, you get a defragger now too. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message