Date: Tue, 19 Mar 1996 23:22:20 -0800 From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: Odd-looking files in lost+found after fsck? Message-ID: <199603200722.XAA09747@freefall.freebsd.org> In-Reply-To: Your message of "Tue, 19 Mar 1996 00:20:08 %2B0100." <199603182320.AAA29294@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>As Brian Tao wrote: > >> 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? > >Trash written all over an i-node block. > >Is this with an `ahc' driver (it's the only one where i've ever seen >this, too)? If so, is this plain 2.1R, or a newer one? Justin was >sure that he's been fixing these kind of problems meanwhile. Its not really a driver specific problem. It all depends on what you were doing when the bus stuffed up. The real problem IMHO is that fsck is pathological in cases where it probably doesn't have to be. Of course I'm also working on making the SCSI drivers more robust to these types of errors too, but someone should go look at fsck. >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE >Never trust an operating system you don't have sources for. ;-) -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603200722.XAA09747>