From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 13:00: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 EA6A816A4CE for ; Fri, 6 Feb 2004 13:00: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 36E8643D3F for ; Fri, 6 Feb 2004 12:59:56 -0800 (PST) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i16Kxpe3038399; Sat, 7 Feb 2004 07:59:51 +1100 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost)i16Kxojt038398; Sat, 7 Feb 2004 07:59:50 +1100 (EST) (envelope-from jeremyp) Date: Sat, 7 Feb 2004 07:59:50 +1100 From: Peter Jeremy To: Claus Guttesen Message-ID: <20040206205950.GU908@cirb503493.alcatel.com.au> References: <20040206072244.GT908@cirb503493.alcatel.com.au> <20040206084458.53207.qmail@web14101.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040206084458.53207.qmail@web14101.mail.yahoo.com> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: 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 21:00:01 -0000 On Fri, Feb 06, 2004 at 09:44:58AM +0100, Claus Guttesen wrote: >>> But it's not my problem. What you mean results in >>> limited available space, >>> but doesn't have any influence on Size summary. >>> Btw I did a newfs with -m 0 >>> so it can't be the reaseon. >> >> This is strongly non-recommended. The UFS >> algorithms are designed on >> the assumption that there are always free blocks. >> When you get below >> 5-10% free space, the performance will degrade >> significantly and you >> will start getting file fragmentation. >> > >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. In general, yes. See /usr/share/doc/smm/05.fastfs/paper.ascii.gz You might be able to get away with a lower minfree in some circumstances depending on your filesystem activity pattern. Peter