From owner-freebsd-questions@FreeBSD.ORG  Mon Aug 15 13:39:06 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: questions@freebsd.org
Delivered-To: freebsd-questions@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0A57216A41F
	for <questions@freebsd.org>; Mon, 15 Aug 2005 13:39:06 +0000 (GMT)
	(envelope-from freminlins@gmail.com)
Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.202])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E38C843D67
	for <questions@freebsd.org>; Mon, 15 Aug 2005 13:39:03 +0000 (GMT)
	(envelope-from freminlins@gmail.com)
Received: by nproxy.gmail.com with SMTP id x37so211985nfc
	for <questions@freebsd.org>; Mon, 15 Aug 2005 06:39:02 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=E2hElVcwh+VLiJn9/i+Qa5dzoJBQpuQZSZ8WNJlI5Qg+5IsaVnhEK64GKam/sLtQzdUTCdg8XYM4HKFpKrA4ZfAr7ytCSepNtK2ZZ4a0Li7cicsRG1syanxvNagEVtxB4v9kHyM/WAucFkZT6eZHs/2/le9ZQAyEcKK9chvvBwE=
Received: by 10.48.239.18 with SMTP id m18mr158249nfh;
	Mon, 15 Aug 2005 06:39:02 -0700 (PDT)
Received: by 10.48.239.6 with HTTP; Mon, 15 Aug 2005 06:39:02 -0700 (PDT)
Message-ID: <eeef1a4c05081506391b6fbb2f@mail.gmail.com>
Date: Mon, 15 Aug 2005 14:39:02 +0100
From: Freminlins <freminlins@gmail.com>
To: Jerry McAllister <jerrymc@clunix.cl.msu.edu>
In-Reply-To: <200508151320.j7FDKCVq025507@clunix.cl.msu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <d396fddf05081421343aeded9d@mail.gmail.com>
	<200508151320.j7FDKCVq025507@clunix.cl.msu.edu>
Cc: Lei Sun <lei.sun@gmail.com>, questions@freebsd.org,
	cpghost <cpghost@cordula.ws>, Glenn Dawson <glenn@antimatter.net>
Subject: Re: disk fragmentation, <0%?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2005 13:39:06 -0000

On 8/15/05, Jerry McAllister <jerrymc@clunix.cl.msu.edu> wrote:
> >

> As someone mentioned, there is a FAQ on this.   You should read it.
>=20
> It is going negative because you have used more than the nominal
> capacity of the slice.   The nominal capacity is the total space
> minus the reserved proportion (usually 8%) that is held out.
> Root is able to write to that space and you have done something
> that got root to write beyond the nominal space.

I'm not sure you are right in this case. I think you need to re-read
the post. I've quoted the relevent part here:
=20
> > Filesystem     Size    Used   Avail Capacity  Mounted on
> > /dev/ar0s1e    248M   -278K    228M    -0%    /tmp

Looking at how the columns line up I have to state that I too have
never seen this behaviour.  As an experiment I over-filled a file
system and here's the results:

Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad0s1f    965M    895M   -7.4M   101%    /tmp

Note capacity is not negative. So that makes three of us in this
thread who have not seen negative capacity on UFS.

I have seen negative capacity when running an old version of FreeBSD
with a very large NFS mount (not enough bits in statfs if I remember
correctly).

> ////jerry

Frem.