From owner-freebsd-hackers Mon Dec 4 02:52:29 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA18360 for hackers-outgoing; Mon, 4 Dec 1995 02:52:29 -0800 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA18355 for ; Mon, 4 Dec 1995 02:52:26 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id CAA08709 for ; Mon, 4 Dec 1995 02:51:07 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA16019; Mon, 4 Dec 1995 10:02:02 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA25767; Mon, 4 Dec 1995 10:02:02 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id JAA07830; Mon, 4 Dec 1995 09:36:09 +0100 From: J Wunsch Message-Id: <199512040836.JAA07830@uriah.heep.sax.de> Subject: Re: HELP -- strange file system corruption under freebsd To: rminnich@Sarnoff.COM (Ron G. Minnich) Date: Mon, 4 Dec 1995 09:36:08 +0100 (MET) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Ron G. Minnich" at Dec 3, 95 02:54:52 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 891 Sender: owner-hackers@freebsd.org Precedence: bulk As Ron G. Minnich wrote: > > my friends at penn are having weird problems on their freebsd boxes. The > machines load and run fine, then at some point the file system gets hosed > and can't be repaired >> It is unclear what actually happens to the filesystem... It just becomes >> corrupted. Next time it happens, we'll examine the inode structures... Perhaps directories or files are being turned into `device nodes'? Seems like a problem with the 2940 driver after SCSI bus timeouts. I've somtimes seen it, too (but only for SCSI buses where more than the disk device is attached). Since it aren't only device nodes, but also have got very weird permissions (including mysterious file flags), i wouldn't suspect 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. ;-)