Date: Tue, 21 Nov 2006 10:27:18 -0000 From: "Lawrence Farr" <freebsd-stable@epcdirect.co.uk> To: "'Kris Kennaway'" <kris@obsecurity.org>, "'Tom Samplonius'" <tom@samplonius.org> Cc: freebsd-stable@freebsd.org Subject: RE: ufs_dirbad: bad dir panic (Was Areca Weirdness) Message-ID: <014a01c70d57$a00f6db0$c806a8c0@lfarr> In-Reply-To: <20061121004429.GA51764@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Kris Kennaway [mailto:kris@obsecurity.org] > 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) > > On Mon, Nov 20, 2006 at 04:29:17PM -0800, Tom Samplonius wrote: > > > > ----- 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. > > 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 > I have been newfs'ing it and starting again, and it will work once, but once unmounted and re-mounted it will panic with ufs_dirbad.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?014a01c70d57$a00f6db0$c806a8c0>