From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 10:57:15 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 B718216A4CE for ; Fri, 6 Feb 2004 10:57:15 -0800 (PST) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id C976F43D1D for ; Fri, 6 Feb 2004 10:57:12 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i16IvBDa050222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Fri, 6 Feb 2004 13:57:12 -0500 (EST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i16IvBOc050219; Fri, 6 Feb 2004 13:57:11 -0500 (EST) (envelope-from wollman) Date: Fri, 6 Feb 2004 13:57:11 -0500 (EST) From: Garrett Wollman Message-Id: <200402061857.i16IvBOc050219@khavrinen.lcs.mit.edu> To: =?iso-8859-1?q?Claus=20Guttesen?= In-Reply-To: <20040206084458.53207.qmail@web14101.mail.yahoo.com> References: <20040206072244.GT908@cirb503493.alcatel.com.au> <20040206084458.53207.qmail@web14101.mail.yahoo.com> X-Spam-Score: -9.9 () IN_REP_TO,REFERENCES X-Scanned-By: MIMEDefang 2.37 X-Mailman-Approved-At: Sat, 07 Feb 2004 04:52:48 -0800 cc: freebsd-current@FreeBSD.ORG Subject: Reserved space (WAS: How to calculate bsdlabel 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: Fri, 06 Feb 2004 18:57:15 -0000 < said: > Does the algorithm(s) rely only on percentage of free > space? On a five TB (netto) filesystem eigth percent > is approx. 410 GB which seems quite alot. A good Data Structures text will prove to you that the efficiency of hashing algorithms of the sort that the UFS block allocator uses depends only on the occupancy ratio and not on the absolute number of free hash slots. -GAWollman