From gfoster@driver.nsta.org  Tue Feb  6 16:32:06 1996
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
Subject: silent panic due to bogosity in FS
X-Send-Pr-Version: 3.2

>Number:         998
>Category:       kern
>Synopsis:       badness in file system silently crashes machine
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb  6 16:40:02 PST 1996
>Closed-Date:    Thu Mar 6 22:51:27 PST 1997
>Last-Modified:  Thu Mar  6 22:52:26 PST 1997
>Originator:     Glen Foster
>Release:        FreeBSD 2.1.0-951104-SNAP i386
>Organization:
Consultant for National Science Teacher's Association
>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.
	
	

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->bde 
Responsible-Changed-By: pst 
Responsible-Changed-When: Wed Feb 7 17:06:32 PST 1996 
Responsible-Changed-Why:  
Responsible-Changed-From-To: bde->freebsd-bugs 
Responsible-Changed-By: bde 
Responsible-Changed-When: Tue Dec 17 03:53:18 PST 1996 
Responsible-Changed-Why:  
Not exactly my area. 
State-Changed-From-To: open->closed 
State-Changed-By: mpp 
State-Changed-When: Thu Mar 6 22:51:27 PST 1997 
State-Changed-Why:  
Not enough info in the PR to determine the exact cause of 
the problem, and all mail to the originator bounces. 
>Unformatted:
