Date: Tue, 6 Feb 1996 19:31:19 -0500 From: Glen Foster <gfoster@driver.nsta.org> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/998: silent panic due to bogosity in FS Message-ID: <199602070031.TAA00684@driver.nsta.org> Resent-Message-ID: <199602070040.QAA28968@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 998 >Category: kern >Synopsis: badness in file system silently crashes machine >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 6 16:40:02 PST 1996 >Last-Modified: >Originator: Glen Foster >Organization: Consultant for National Science Teacher's Association >Release: FreeBSD 2.1.0-951104-SNAP i386 >Environment: news server, lightly loaded otherwise, NCR810-based SCSI, single Seagate Barracuda 4.3GB disk, other SCSI: cd-rom, DAT >Description: A corrupted inode in a file system, in this case the one used for the news spool causes the system to lock up with the drive activity light solidly lit and shortly thereafter crash without a panic message, crash dump, or entering the kernel debugger. >How-To-Repeat: Anything that touches the inode, including ls and dump. >Fix: Doing a clri on the inode of a parent to this directory and subsequent fsck eliminates the crash. A clri on the inode itself does not. Until the corrupted inode appeared the system was extremely reliable. Corruption appears to have been caused by innd 1.4 compiled from the port on the system in question. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602070031.TAA00684>