From owner-freebsd-bugs  Sat May  6 14:54:17 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id OAA22691
          for bugs-outgoing; Sat, 6 May 1995 14:54:17 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA22682
          for <freebsd-bugs@freebsd.org>; Sat, 6 May 1995 14:54:12 -0700
Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id OAA00174; Sat, 6 May 1995 14:57:06 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id OAA00397; Sat, 6 May 1995 14:54:03 -0700
Message-Id: <199505062154.OAA00397@corbin.Root.COM>
To: Heikki Suonsivu <hsu@cs.hut.fi>
cc: freebsd-bugs@FreeBSD.org
Subject: Re: -current flakey for last couple of days 
In-reply-to: Your message of "Sun, 07 May 95 00:32:37 +0300."
             <199505062132.AA00618@cardhu.cs.hut.fi> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sat, 06 May 1995 14:54:01 -0700
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

>This system has been panicing daily, though it is in heavy use, full news
>feed and 10-20 users.  Most often it panics on "bad dir" (filed PR
>earlier).

   If the inode is always the same one, this is likely caused by fsck not
detecting the problem (and thus not fixing it). I've seen this before on
1.1.5, and perhaps naively thought that it was fixed in the 4.4-lite version
of fsck.

-DG