From owner-freebsd-stable@FreeBSD.ORG Tue Nov 21 00:44:44 2006 Return-Path: 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 2DB0216A417 for ; Tue, 21 Nov 2006 00:44:44 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF55243D46 for ; Tue, 21 Nov 2006 00:44:24 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id B7AAA1A4D84; Mon, 20 Nov 2006 16:44:43 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D1782513A1; Mon, 20 Nov 2006 19:44:29 -0500 (EST) Date: Mon, 20 Nov 2006 19:44:29 -0500 From: Kris Kennaway To: Tom Samplonius Message-ID: <20061121004429.GA51764@xor.obsecurity.org> References: <30064779.31164068868905.JavaMail.root@ly.sdf.com> <12759622.51164068957233.JavaMail.root@ly.sdf.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline In-Reply-To: <12759622.51164068957233.JavaMail.root@ly.sdf.com> User-Agent: Mutt/1.4.2.2i Cc: Lawrence Farr , freebsd-stable@freebsd.org, Kris Kennaway 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Nov 2006 00:44:44 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 20, 2006 at 04:29:17PM -0800, Tom Samplonius wrote: >=20 > ----- Kris Kennaway 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: > > >=20 > > > 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 > >=20 > > Run fsck -fy on the filesystem, this is a common symptom of a > > corrupted filesystem. >=20 > I think the OP knows the filesystem is corrupted. The problem is why d= oes the filesystem get corrupted? The OP says he can corrupt the filesyste= m on demand after a newfs. So it could be the Areca driver, or even bad ha= rdware. My point is that this panic can happen when your filesystem becomes corrupted, and the panic keeps happening during "normal" filesystem operations until you forcibly fsck it, at which point the panic goes away. Kris --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFYkvtWry0BWjoQKURAkAhAJ9dJur00AHQmrIqAiCgf9NzZdgj5gCfeUEC pG/sJx3KHdAxipOyaZcP7IA= =clo9 -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ--