From owner-freebsd-questions@FreeBSD.ORG Mon Aug 15 16:36:03 2005 Return-Path: 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 154E816A41F for ; Mon, 15 Aug 2005 16:36:03 +0000 (GMT) (envelope-from lei.sun@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74CA843D49 for ; Mon, 15 Aug 2005 16:36:02 +0000 (GMT) (envelope-from lei.sun@gmail.com) Received: by wproxy.gmail.com with SMTP id 36so1043435wra for ; Mon, 15 Aug 2005 09:36:01 -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=JUAJ2N0HMATFtFd0maHbrQbdDcaiRLPFCq8MT9pqFzAOhvfQKrOAWEgHwPLNJGrJKuj8B4HhYfi2mof/UGTPUEz3l74D8N55XE921DNhgPBf2QjmP5K0mGoc+xTGf8DqD7A2svUCdbMmULN7dwKMATvzqIHizl0CAIZMWLpX1Ts= Received: by 10.54.46.5 with SMTP id t5mr2526830wrt; Mon, 15 Aug 2005 09:36:01 -0700 (PDT) Received: by 10.54.6.70 with HTTP; Mon, 15 Aug 2005 09:36:00 -0700 (PDT) Message-ID: Date: Mon, 15 Aug 2005 09:36:00 -0700 From: Lei Sun To: Freminlins In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200508151320.j7FDKCVq025507@clunix.cl.msu.edu> Cc: Jerry McAllister , questions@freebsd.org, cpghost , Glenn Dawson Subject: Re: disk fragmentation, <0%? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Aug 2005 16:36:03 -0000 This happened, after I tested the atacontrol to rebuild the raid1. The /tmp partition doesn't have anything but several empty directories crea= ted. and I have the clear /tmp directive in the rc.conf, which will clean up the /tmp everytime when system boot up. So that was really wierd. as it never happened this way the previous time that I was rebuilding the raid1. Thanks Lei On 8/15/05, Freminlins wrote: > On 8/15/05, Jerry McAllister wrote: > > > >=20 > > As someone mentioned, there is a FAQ on this. You should read it. > > > > 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. >=20 > 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 >=20 > 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: >=20 > Filesystem Size Used Avail Capacity Mounted on > /dev/ad0s1f 965M 895M -7.4M 101% /tmp >=20 > Note capacity is not negative. So that makes three of us in this > thread who have not seen negative capacity on UFS. >=20 > 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). >=20 > > ////jerry >=20 > Frem. >