From owner-freebsd-current  Wed Mar 19 16:38:14 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA05950
          for current-outgoing; Wed, 19 Mar 1997 16:38:14 -0800 (PST)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA05945
          for <freebsd-current@freebsd.org>; Wed, 19 Mar 1997 16:38:11 -0800 (PST)
Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.4/8.7.3) id QAA19767; Wed, 19 Mar 1997 16:36:54 -0800 (PST)
Date: Wed, 19 Mar 1997 16:36:54 -0800 (PST)
Message-Id: <199703200036.QAA19767@vader.cs.berkeley.edu>
To: proff@suburbia.net
CC: freebsd-current@freebsd.org
In-reply-to: <19970319142735.17068.qmail@suburbia.net> (proff@suburbia.net)
Subject: Re: file sizes
From: asami@vader.cs.berkeley.edu (Satoshi Asami)
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * ls -l /usr/share/mk
 :
 * -r------wx  255 1671180  1671192  71777085445571048 Aug 24 09:30 bsd.kern.mk
 :

Seems like this directory is quite messed up.  Try "ls -lo" too,
you'll probably see a lot of undeletable files.  This is a hardware or
disk driver problem.

I saw something like this when one of my disks went south and totally
confused the kernel, which managed to scramble the other (healthy)
disk.  You'll have several "bad inodes" and stuff, so just mv them all 
into a separate directory and run fsck manually in single-user mode.

Satoshi