From owner-freebsd-hackers  Tue Mar 19 08:34:26 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA13409
          for hackers-outgoing; Tue, 19 Mar 1996 08:34:26 -0800 (PST)
Received: from cabal.io.org (cabal.io.org [198.133.36.103])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA13380
          Tue, 19 Mar 1996 08:34:15 -0800 (PST)
Received: (from taob@localhost) by cabal.io.org (8.7.4/8.7.4) id LAA03805; Tue, 19 Mar 1996 11:32:57 -0500 (EST)
Date: Tue, 19 Mar 1996 11:32:57 -0500 (EST)
From: Brian Tao <taob@io.org>
To: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
cc: FREEBSD-HACKERS-L <freebsd-hackers@freebsd.org>
Subject: Re: Odd-looking files in lost+found after fsck? 
In-Reply-To: <199603191612.IAA11733@freefall.freebsd.org>
Message-ID: <Pine.BSF.3.91.960319111503.2083J-100000@cabal.io.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 19 Mar 1996, Justin T. Gibbs wrote:
>
> Fsck will occasionally do this just for kicks when it incounters
> corrupt inode information.  What disk controller are you using?

    NCR53c810.  fsck was spewing something nasty about bad/duplicate
inodes when it was churning through one that disk.  It would be nice
if the fsck output was logged somewhere for later perusal.
--
Brian Tao (BT300, taob@io.org)
System and Network Administrator, Internex Online Inc.
"Though this be madness, yet there is method in't"