From owner-freebsd-questions@FreeBSD.ORG Mon Apr 21 13:12:57 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 263F337B404 for ; Mon, 21 Apr 2003 13:12:57 -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 2434243FDD for ; Mon, 21 Apr 2003 13:12:56 -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 h3LKBBvE030045; Mon, 21 Apr 2003 21:11:12 +0100 (BST) (envelope-from freebsd@sgeine.net) From: "Jesse Geddis" To: "Dan Nelson" Date: Mon, 21 Apr 2003 13:13:43 -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) In-Reply-To: <20030421201002.GH28595@dan.emsphone.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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 20:12:57 -0000 sure, I should say i've never seen it report properly since we added another disk shelf to our netapp last friday. i'm assuming the problem arises when the filesystem achives 1tb or greater. -----Original Message----- From: Dan Nelson [mailto:dnelson@allantgroup.com] Sent: Monday, April 21, 2003 1:10 PM To: Jesse Geddis Cc: freebsd-questions@freebsd.org Subject: Re: nfs filesystem size In the last episode (Apr 21), Jesse Geddis said: > 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 =) I was working on a fix when my filesystem df stats suddenly reverted back to normal, so I lost my test case :) If you're willing to do some kernel rebuilding, start adding printfs inside nfs_statfs and related functions, and determine exactly where the sign change occurs. -- Dan Nelson dnelson@allantgroup.com