From owner-freebsd-stable@FreeBSD.ORG  Tue Nov 21 00:24:56 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 5FD6716A415
	for <freebsd-stable@freebsd.org>; Tue, 21 Nov 2006 00:24:56 +0000 (UTC)
	(envelope-from tom@samplonius.org)
Received: from ly.sdf.com (ly.sdf.com [216.113.193.83])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3228F43D60
	for <freebsd-stable@freebsd.org>; Tue, 21 Nov 2006 00:24:37 +0000 (GMT)
	(envelope-from tom@samplonius.org)
Received: from localhost (localhost [127.0.0.1])
	by ly.sdf.com (Postfix) with ESMTP id 47DF410C665;
	Mon, 20 Nov 2006 16:29:18 -0800 (PST)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Mon Nov 20 16:29:17 2006
X-DSPAM-Confidence: 0.9997
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 4562485d103481260912508
X-DSPAM-Factors: 27,
X-Virus-Scanned: amavisd-new at 
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-10 required=6.6
	tests=[ALL_TRUSTED=-1.8, AWL=0.289, BAYES_00=-2.599, DSPAM_HAM=-0.1]
Received: from ly.sdf.com ([127.0.0.1])
	by localhost (ly.sdf.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sTGgWGEkYLeu; Mon, 20 Nov 2006 16:29:17 -0800 (PST)
Received: from ly.sdf.com (ly.sdf.com [216.113.193.83])
	by ly.sdf.com (Postfix) with ESMTP id 56C1810C67B;
	Mon, 20 Nov 2006 16:29:17 -0800 (PST)
Message-ID: <12759622.51164068957233.JavaMail.root@ly.sdf.com>
Date: Mon, 20 Nov 2006 16:29:17 -0800 (PST)
From: Tom Samplonius <tom@samplonius.org>
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <30064779.31164068868905.JavaMail.root@ly.sdf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: Lawrence Farr <freebsd-stable@epcdirect.co.uk>, freebsd-stable@freebsd.org
Subject: Re: ufs_dirbad: bad dir panic (Was Areca Weirdness)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Nov 2006 00:24:56 -0000


----- Kris Kennaway <kris@obsecurity.org> wrote:
> > > > > >> If I newfs it, and copy data to it, I have no problem
> > > initially.
> > I can repeat this 100% now, by copying data onto the drive then
> unmounting
> > and remounting it. I have a core dump if anyone can tell me what
> info to
> > get from it:
> > 
> >   Version String: FreeBSD 6.2-PRERELEASE #0: Wed Nov 15 19:57:01 GMT
> 2006
> >     root@monitor.shorewood-epc.co.uk:/usr/obj/usr/src/sys/P6NOUSB
> >   Panic String: ufs_dirbad: bad dir
> 
> Run fsck -fy on the filesystem, this is a common symptom of a
> corrupted filesystem.

  I think the OP knows the filesystem is corrupted.  The problem is why does the filesystem get corrupted?  The OP says he can corrupt the filesystem on demand after a newfs.  So it could be the Areca driver, or even bad hardware.

Tom