From owner-freebsd-bugs Sat Jan 13 02:10:08 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA17437 for bugs-outgoing; Sat, 13 Jan 1996 02:10:08 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA17423 Sat, 13 Jan 1996 02:10:03 -0800 (PST) Resent-Date: Sat, 13 Jan 1996 02:10:03 -0800 (PST) Resent-Message-Id: <199601131010.CAA17423@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:"from sunrise.cs.berkeley.edu (sunrise.CS.Berkeley.EDU [128.32.38.121]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA17287 for" ; Sat, 13 Jan 1996 02:06:47.-0800 (PST) Received: (from asami@localhost) by sunrise.cs.berkeley.edu (8.6.12/8.6.12) id CAA07932; Sat, 13 Jan 1996 02:08:43 -0800 Message-Id: <199601131008.CAA07932@sunrise.cs.berkeley.edu> Date: Sat, 13 Jan 1996 02:08:43 -0800 From: asami@cs.berkeley.edu To: FreeBSD-gnats-submit@freebsd.org Cc: nisha@sunrise.cs.berkeley.edu X-Send-Pr-Version: 3.2 Subject: bin/943: df gets confused by huge filesystems Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 943 >Category: bin >Synopsis: df can't handle large filesystems >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 13 02:10:01 PST 1996 >Last-Modified: >Originator: Satoshi Asami >Organization: University of California at Berkeley >Release: FreeBSD 2.1-STABLE i386 (<== this is a lie, it's 2.1R) >Environment: 2.1R with a striped disk driver (ccd) taken from NetBSD (the kernel is modified, but I don't think that will make any difference to this problem). >Description: df seems to get confused when there is too many blocks, e.g.: >How-To-Repeat: Get yourself a disk array. :) >Fix: If I knew, I'd commit it! >Audit-Trail: >Unformatted: >> df -k -t local Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0a 32254 16670 13002 56% / /dev/sd0e 15391 3071 11088 22% /var /dev/sd0f 530207 276313 211477 57% /usr /dev/ccd0c 19801168 205004 -3462766 -6% /mnt ^^^^^^^^^^^^^^ I took a look at the source but can't for the life of myself can't figure out why it's only the "avail" and "capacity" fields that get screwed up. For instance, the "1K-blocks" field is handled in an identical way!