From owner-freebsd-questions  Sun Jan 19 13:26:38 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id NAA19285
          for questions-outgoing; Sun, 19 Jan 1997 13:26:38 -0800 (PST)
Received: from ns2.netxpress.com (root@ns.netxpress.com [205.218.168.10])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA19280
          for <freebsd-questions@freebsd.org>; Sun, 19 Jan 1997 13:26:33 -0800 (PST)
Received: (from dave@localhost) by ns2.netxpress.com (8.8.2/8.8.2) id PAA01905; Sun, 19 Jan 1997 15:23:54 -0600 (CST)
Date: Sun, 19 Jan 1997 15:23:54 -0600 (CST)
From: Dave <dave@netxpress.com>
To: freebsd-questions@freebsd.org
Message-ID: <Pine.BSF.3.91.970119152015.1444A-100000@ns2.netxpress.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

After an apparent memory problem on our intel venus pentium pro-200mhz w/ 
256k cache motherboard, we were left with the following file after 
fsck'ing...This is with 2.1.6-RELEASE.  The configuration is adaptec 
wide/differential scsi controller, 3 4.3gig micropolis drives, intel 
etherexpress pro 10/100 (everything pci).  

here is what we see when we ls this users home dir:
# ls -la /usr/users/necro99
c--Sr-x-wT  3 1713384482  171649380  100, 539754598 Jun  1  1975 
/usr/users/necro99

any comments?  files in lost+found look evil like this too...
I'm going to backup the fs and reload it clean, but I would like to know 
if this is fixed in a later release in case our server crashes again.