From owner-freebsd-bugs  Tue Feb  6 16:40:06 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA28983
          for bugs-outgoing; Tue, 6 Feb 1996 16:40:06 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA28968
          Tue, 6 Feb 1996 16:40:03 -0800 (PST)
Resent-Date: Tue, 6 Feb 1996 16:40:03 -0800 (PST)
Resent-Message-Id: <199602070040.QAA28968@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, gfoster@driver.nsta.org
Received: from driver.nsta.org (driver.nsta.org [199.0.2.2])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA28503
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 6 Feb 1996 16:32:06 -0800 (PST)
Received: (from gfoster@localhost) by driver.nsta.org (8.6.12/8.6.12) id TAA00684; Tue, 6 Feb 1996 19:31:19 -0500
Message-Id: <199602070031.TAA00684@driver.nsta.org>
Date: Tue, 6 Feb 1996 19:31:19 -0500
From: Glen Foster <gfoster@driver.nsta.org>
Reply-To: gfoster@driver.nsta.org
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: kern/998: silent panic due to bogosity in FS
Sender: owner-bugs@freebsd.org
Precedence: bulk


>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: