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? Message-ID: <Pine.BSF.3.91.960319111503.2083J-100000@cabal.io.org> In-Reply-To: <199603191612.IAA11733@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960319111503.2083J-100000>