From owner-freebsd-questions@FreeBSD.ORG Mon Apr 21 12:28:31 2003 Return-Path: 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 B2C7C37B401 for ; Mon, 21 Apr 2003 12:28:31 -0700 (PDT) Received: from skye.sgeine.net (adsl-63-198-133-39.dsl.lsan03.pacbell.net [63.198.133.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF09F43FDF for ; Mon, 21 Apr 2003 12:28:30 -0700 (PDT) (envelope-from freebsd@sgeine.net) Received: from perth (adsl-64-161-165-243.dsl.lsan03.pacbell.net [64.161.165.243]) by skye.sgeine.net (8.12.9/8.12.9) with SMTP id h3LJQivE029959; Mon, 21 Apr 2003 20:26:44 +0100 (BST) (envelope-from freebsd@sgeine.net) From: "Jesse Geddis" To: "Dan Nelson" Date: Mon, 21 Apr 2003 12:29:16 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: <20030421191537.GG28595@dan.emsphone.com> cc: freebsd-questions@freebsd.org Subject: RE: nfs filesystem size X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd@sgeine.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2003 19:28:32 -0000 Dan, Yes, it only appears to affect the reporting and not the actual reading/writing to the filesystem. Is there an adjustment I can make to correct it? Thanks again =) -----Original Message----- From: Dan Nelson [mailto:dnelson@allantgroup.com] Sent: Monday, April 21, 2003 12:16 PM To: Jesse Geddis Cc: freebsd-questions@freebsd.org Subject: Re: nfs filesystem size In the last episode (Apr 21), Jesse Geddis said: > We have a NetApp FAS940 with a current storage size of 1.266 TB. FreeBSD is > reporting the following: > > Filesystem Size Used Avail Capacity Mounted on > /dev/da0s1a 2.0G 56M 1.8G 3% / > /dev/da0s1f 9.8G 1.9G 7.1G 21% /usr > /dev/da0s1g 5.2G 82M 4.7G 2% /usr/home > /dev/da0s1e 15G 161M 13G 1% /var > procfs 4.0K 4.0K 0B 100% /proc > 10.0.0.100:/vol/www01 -811.2G 465G 771G -57% /www > > is this a limitation of how large a filesystem freebsd can report or > are we running into something else that is fixable here? Thanks in > advance. I think I traced it to a variable overflow in nfs_vfsops.c:nfs_statfs(). I have a 1.4TB filesystem that occasionally (but not always) goes negative too. It just affects the results of the statfs/statvfs() calls, so the only thing it really hurts is 'df'. Filesystem Size Used Avail Capacity Mounted on novell1:/vol1 1.4T 1.1T 314G 78% /a/novell1/vol1 -- Dan Nelson dnelson@allantgroup.com