Bug 998 - badness in file system silently crashes machine
Summary: badness in file system silently crashes machine
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1996-02-07 00:40 UTC by Glen Foster
Modified: 1997-03-07 06:52 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Glen Foster 1996-02-07 00:40:02 UTC 
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.

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.
How-To-Repeat: Anything that touches the inode, including ls and
dump.
Comment 1 pst freebsd_committer freebsd_triage 1996-02-08 01:06:32 UTC 
Responsible Changed
From-To: freebsd-bugs->bde
Comment 2 Bruce Evans freebsd_committer freebsd_triage 1996-12-17 11:53:18 UTC 
Responsible Changed
From-To: bde->freebsd-bugs

Not exactly my area.
Comment 3 mpp freebsd_committer freebsd_triage 1997-03-07 06:51:27 UTC 
State Changed
From-To: open->closed

Not enough info in the PR to determine the exact cause of 
the problem, and all mail to the originator bounces.