ufs_dirbad: bad dir panic (Was Areca Weirdness)
freebsd-stable at epcdirect.co.uk
Tue Nov 21 02:27:25 PST 2006
> -----Original Message-----
> From: Kris Kennaway [mailto:kris at obsecurity.org]
> Sent: 21 November 2006 00:44
> To: Tom Samplonius
> Cc: Kris Kennaway; freebsd-stable at 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 at 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 at 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
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.
More information about the freebsd-stable