Date: Mon, 20 Nov 2006 16:29:17 -0800 (PST) From: Tom Samplonius <tom@samplonius.org> To: Kris Kennaway <kris@obsecurity.org> Cc: Lawrence Farr <freebsd-stable@epcdirect.co.uk>, freebsd-stable@freebsd.org Subject: Re: ufs_dirbad: bad dir panic (Was Areca Weirdness) Message-ID: <12759622.51164068957233.JavaMail.root@ly.sdf.com> In-Reply-To: <30064779.31164068868905.JavaMail.root@ly.sdf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12759622.51164068957233.JavaMail.root>