Subject: df -k incorrect results?
To: None <port-mac68k@NetBSD.ORG>
From: Wenchi Liao <wliao@midway.uchicago.edu>
List: port-mac68k
Date: 04/29/1998 01:55:07
Hello.

I have a Centris 605 with bsd 1.3.1 generic. 32M ram, 1.25G hard
drive.  When I run disklabel, I get this (slightly edited):
	c:  2503872  0   unused  0     0       # (Cyl.    0 - 6841*)
So the entire drive is roughly 1G. Minus a tiny mac partition, and the
total netbsd usable drive space is under a gig. I'm assuming "size" is
given in sectors, and disklabel reports 512 bytes/sector. Which
corresponds nicely to the known hard drive size (or at least according
to hd sc setup).

Now, I run df -k:
	Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
	/dev/sd0a      144933    36239    94200    28%    /
	/dev/sd0f      730675   467435   190172    71%    /usr
	/dev/sd0g      341561   244061    63343    79%    /var
	/dev/sd0h     1066464   759282   200535    79%    /opt
	/dev/sd0e      389624   341573     9088    97%    /tmp
	kernfs              1        1        0   100%    /kern
	procfs              4        4        0   100%    /proc

Erp. This reports one partition is a gig; the entire drive is over 2
gigs! A quick run to /tmp shows even wierder results:
	sage# pwd
	/tmp
	sage# du -sk
	12      .

This is using the df from the distribution sets. Hoping for better
results, I grabbed gnu's fileutils and ran their df. Same results.

I've briefly skimmed the archived mailing list. Is this a known
problem? or am I just missing something really obvious?

WL