Lindsay,

I was having the same problem on an almost identical setup. After installing
and reinstalling several times I found that this problem occured in both
versions 1.4 and 1.4.1, but only if I created the filesystem using mkfs
1.46. Keeping all other things equal, I reinstalled 1.4.1 from the ground up
using mkfs 1.45 and this seemed to fix things. df reports things as it
should.

John M

----------
>From: Lindsay Adams <lindsay.adams@mountaingate.com>
>To: port-mac68k@netbsd.org
>Subject: DF ?
>Date: Mon, Oct 4, 1999, 2:51 PM
>

> yes, i am asking about df and why it seems all screwed up.
>
> Before i go any further, i did search through ALL of the 99 mailings
> on the website, before posing this to the list.
> I found a few references to it being buggy in 1.3, one noting that it
> still might be wrong in 1.4.
>
> here is what i have.
>
> A fresh, really fresh, install of 1.4.1 on a Quadra 660 AV onto a 500Mb HD.
> in all cases, filesystems were created using the latest version of
> mkfs in the macos
>
> I installed the required bnaries, and the man and misc packages as well.
> the drive is partitioned 24 Mb swap, the rest Root & Usr.
>
> I can boot into it just fine, but here is what i get when i df:
> ---
>
> dingo: {1} df
> Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
> /dev/sd1a   -571727784 -572548692 -285603698   103%    /
> kernfs               2        2        0   100%    /kern
> procfs               8        8        0   100%    /proc
> ---
>
> What? i haven't done anything but configure the ethernet and the
> capacity is 103%?
> Thought that was strange, did 'du -c > a.a &' and when it returned, it said:
> 59366 /
>
> roughly 59M, am i right?
>
> tried on a 1 gig drive, that reports the following from the minishell
> in the installer:
>
> sd2a Root 'NetBSD Root at 20192 size 400000 (512 bytes/sect = 200Meg
partition)
> sd2g Usr  'Net BSD Usr' at 420192 size 1560000 (= 780Meg partition)
>
> okay, that's how i partitioned it, also have a 24 Meg swap.
>
> mount the partitions as /temp/root and /temp/usr BOTH EMPTY and do df and:
> ----
> dingo: {32} df
> Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
> /dev/sd1a   -285863892 -286274324 -142801871   103%    /
> kernfs              1        1        0   100%    /kern
> procfs              4        4        0   100%    /proc
> /dev/sd2a   421465123 421271599 -41952989   111%    /temp/root
> /dev/sd2g      755061        8   679546     0%    /temp/usr
> ----
>
> okay, that is just unacceptable.  the kicker is that the system
> immediately starts complaining about being full.
>
> What on earth have i screwed up? If i haven't screwed anything up,
> what do i do to fix it?
> can i run newfs on the 1G drive and then run the installer on it?
> What to do, what to do.
>
> Thanks!
> _______________________________________________________
> Lindsay Adams                                IS Manager
> Mountaingate Imaging Systems Corp.    775 824-2611
>    I.S., and you thought water torture was bad.
> _______________________________________________________
>