From owner-freebsd-questions@FreeBSD.ORG Wed Feb 4 08:12:36 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 EC0031065679 for ; Wed, 4 Feb 2009 08:12:36 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id C640A8FC24 for ; Wed, 4 Feb 2009 08:12:36 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n148CTBx093566 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 4 Feb 2009 00:12:30 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n148CTwt093565; Wed, 4 Feb 2009 00:12:29 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA13921; Wed, 4 Feb 09 00:07:04 PST Date: Wed, 04 Feb 2009 00:08:25 -0800 From: perryh@pluto.rain.com To: john@zog.net, dnelson@allantgroup.com Message-Id: <49894cf9.J2VbLPqLSoDq7yay%perryh@pluto.rain.com> References: <158E6ABD-6BCF-4222-AD59-9B43FE6832D5@zog.net> <20090203215326.GN75802@dan.emsphone.com> In-Reply-To: <20090203215326.GN75802@dan.emsphone.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: NFSv2 Wrong FS Size 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, 04 Feb 2009 08:12:37 -0000 > 1755708928*1024/512 = 3511417856 blocks. This number is larger > than 2^31, which techinically isn't a problem because the NFSv2 > spec says that the filesystem size is unsigned. FreeBSD treats it > as signed, though, so it can display "negative" free space when > root starts using its 8% reserve, so your unsigned 3511417856 gets > printed as a signed -783549440, which messes everything up. ... > you could rebuild "df" to print its numbers as unsigned instead of > signed. Just watch out if your local filesystems start eating > into their 8% reserve, since they'll start reporting huge values. Or patch "df" to print local filesystem sizes as signed -- so that the reserve reporting still works -- and NFS as unsigned to match the spec.