From owner-freebsd-questions@FreeBSD.ORG Wed May 27 17:12:50 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBCDD1065A5D for ; Wed, 27 May 2009 17:12:50 +0000 (UTC) (envelope-from psteele@webmail.maxiscale.com) Received: from k2smtpout04-01.prod.mesa1.secureserver.net (k2smtpout04-01.prod.mesa1.secureserver.net [64.202.189.166]) by mx1.freebsd.org (Postfix) with SMTP id 96FE08FC23 for ; Wed, 27 May 2009 17:12:50 +0000 (UTC) (envelope-from psteele@webmail.maxiscale.com) Received: (qmail 30761 invoked from network); 27 May 2009 17:12:49 -0000 Received: from unknown (HELO owa.webmail.maxiscale.com) (72.167.52.135) by k2smtpout04-01.prod.mesa1.secureserver.net (64.202.189.166) with ESMTP; 27 May 2009 17:12:49 -0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Wed, 27 May 2009 10:12:49 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Is this a gmirror bug? Thread-Index: AcneV+Tk8/CRr+7tRWKtomK7n84IRAAliXXA References: <20090526230522.GH49013@hal.rescomp.berkeley.edu> <20090527011302.98954329.freebsd@edvax.de> From: "Peter Steele" To: Subject: RE: Is this a gmirror bug? 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: Wed, 27 May 2009 17:12:52 -0000 >Wouldn't it look like > >Filesystem 1K-blocks Used Avail Capacity Mounted on >/dev/mirror/gm0d 4058062 -377792 4111210 110% /tmp >/dev/mirror/gm0e 15231278 -113942 14126718 101% /var > >then? I always assumed that a disk occupation > 100% would go into >this reserved area, which would turn the Capacity field to be more >than 100%, and not less than 0%? This is the case when I have more >data on a UFS partition than it "is allowed to"... I've seen this before a few times, but never something less than 0%. I've reimaged the system to correct it. Will have to see if it happens again...