From owner-freebsd-questions Fri Sep 3 12:58:45 1999 Delivered-To: freebsd-questions@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id D6B5014E30 for ; Fri, 3 Sep 1999 12:58:36 -0700 (PDT) (envelope-from dscheidt@tumbolia.com) Received: (qmail 15834 invoked from network); 3 Sep 1999 19:57:58 -0000 Received: from shell-3.enteract.com (dscheidt@207.229.143.42) by pop3-3.enteract.com with SMTP; 3 Sep 1999 19:57:57 -0000 Date: Fri, 3 Sep 1999 14:57:57 -0500 (CDT) From: David Scheidt X-Sender: dscheidt@shell-3.enteract.com To: Steve Friedrich Cc: FreeBSD Questions Subject: Re: df inconsistency In-Reply-To: <199909031914.PAA21107@laker.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Sep 1999, Steve Friedrich wrote: > df output on my system: > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd1s1e 1113967 929244 95606 91% /usr > > Problem is that (total blocks) - (used blocks) does not equal > (available blocks) > 1113967 - 929244 = 184723 = 83% > > 95606/1113967 = 9% (so the inverse is 91%) > > So it appears that 89117 are "unavailable" but not counted as "used". Yup. It is the space that FFS reserves for its own use. See the newfs(8) and tunefs(8) man pages. It is a tunable, which should be left alone unless you know what you are doing. FFS reserves the space so that it can do effective fragmentation avoidance. If you want to know more, see http://docs.freebsd.org/cgi/getmsg.cgi?fetch=486037+0+current/freebsd-hackers David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message