Date: Tue, 21 Nov 2006 16:06:50 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Lawrence Farr <freebsd-stable@epcdirect.co.uk> Cc: freebsd-stable@freebsd.org, 'Tom Samplonius' <tom@samplonius.org>, 'Kris Kennaway' <kris@obsecurity.org> Subject: Re: ufs_dirbad: bad dir panic (Was Areca Weirdness) Message-ID: <20061121210648.GA90974@xor.obsecurity.org> In-Reply-To: <014a01c70d57$a00f6db0$c806a8c0@lfarr> References: <20061121004429.GA51764@xor.obsecurity.org> <014a01c70d57$a00f6db0$c806a8c0@lfarr>
next in thread | previous in thread | raw e-mail | index | archive | help
--Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 21, 2006 at 10:27:18AM -0000, Lawrence Farr wrote: > =20 >=20 > > -----Original Message----- > > From: Kris Kennaway [mailto:kris@obsecurity.org]=20 > > Sent: 21 November 2006 00:44 > > To: Tom Samplonius > > Cc: Kris Kennaway; freebsd-stable@freebsd.org; Lawrence Farr > > Subject: Re: ufs_dirbad: bad dir panic (Was Areca Weirdness) > >=20 > > On Mon, Nov 20, 2006 at 04:29:17PM -0800, Tom Samplonius wrote: > > >=20 > > > ----- 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: > > > > >=20 > > > > > Version String: FreeBSD 6.2-PRERELEASE #0: Wed Nov 15=20 > > 19:57:01 GMT > > > > 2006 > > > > > =20 > > 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=20 > > problem is why does the filesystem get corrupted? The OP=20 > > says he can corrupt the filesystem on demand after a newfs. =20 > > So it could be the Areca driver, or even bad hardware. > >=20 > > 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. > >=20 > > Kris > >=20 >=20 > I have been newfs'ing it and starting again, and it will work once, but= =20 > once unmounted and re-mounted it will panic with ufs_dirbad. OK, that's a different matter then. One thing you could try would be to write known data directly to the device and then read it back or verify the md5 sum and try to identify the failure mode. I'd try to rule out hardware problems too. Kris --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFY2poWry0BWjoQKURAk4YAKCg5r6t5epRUn9gr6+viWCQ4/nLpgCeIyD1 Wz7yRdGpy4fmymIJU82+IwI= =bUbY -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061121210648.GA90974>