From owner-freebsd-hackers  Wed Sep  4 11:27:14 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA25349
          for hackers-outgoing; Wed, 4 Sep 1996 11:27:14 -0700 (PDT)
Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA25342
          for <FreeBSD-hackers@freebsd.org>; Wed, 4 Sep 1996 11:27:10 -0700 (PDT)
Received: by gvr.win.tue.nl (8.6.13/1.53)
    id UAA10801; Wed, 4 Sep 1996 20:27:06 +0200
From: guido@gvr.win.tue.nl (Guido van Rooij)
Message-Id: <199609041827.UAA10801@gvr.win.tue.nl>
Subject: fsck incorrectly found no errors
To: FreeBSD-hackers@freebsd.org (FreeBSD-hackers)
Date: Wed, 4 Sep 1996 20:27:05 +0200 (MET DST)
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

After a crash, we had a file system that had to be repaired by
fsck. Shortly after mounting the corrected file system the
syetm died with a 'mangled entry' panic. 
After this panic, fsck every time reports the file system to be okay,
while after accessing a certain directory on this filesystem you
would get the same panic again. This all took place on a 2.0.5
system with Terry's patch applied to fsck.

I've made a dump (with dd) of the particular filesystem. It is 800MB
big and, because it contains rather sensitive data I cannot give it
away. I am planning to vnconfig the raw image and then run fsdb
on it.  If anyone has suggestions on what to look for...

I've seen other people reporting this bug so I first like to know
if something has been fixed in this area. (e.g. look with the
search engine in the stable mailiong list for ccd and fsck).

-Guido