From owner-freebsd-hackers Tue Mar 19 08:12:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA11741 for hackers-outgoing; Tue, 19 Mar 1996 08:12:51 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA11733 Tue, 19 Mar 1996 08:12:46 -0800 (PST) Message-Id: <199603191612.IAA11733@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Brian Tao cc: FREEBSD-HACKERS-L Subject: Re: Odd-looking files in lost+found after fsck? In-reply-to: Your message of "Mon, 18 Mar 1996 13:33:15 EST." Date: Tue, 19 Mar 1996 08:12:46 -0800 From: "Justin T. Gibbs" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The filesystem holds our entire Apache document tree. The first >two regular files are log files for one of our virtual domains, and I >don't know what the third is. But what could have created the two >block special files? A pipe? Fsck will occasionally do this just for kicks when it incounters corrupt inode information. What disk controller are you using? >-- >Brian Tao (BT300, taob@io.org) >Systems Administrator, Internex Online Inc. "Though this be madness, yet there is method in't" > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================