Date: Fri, 3 Mar 2006 03:50:06 GMT From: Robert Watson <rwatson@FreeBSD.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/93942: panic: ufs_dirbad: bad dir Message-ID: <200603030350.k233o6LF000920@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/93942; it has been noted by GNATS. From: Robert Watson <rwatson@FreeBSD.org> To: Yarema <yds@CoolRat.org> Cc: FreeBSD-gnats-submit@freebsd.org, FreeBSD-current@freebsd.org, David Rhodus <drhodus@machdep.com>, Dennis Koegel <amf@hobbit.neveragain.de>, Martin Machacek <m@m3a.net>, Kris Kennaway <kris@obsecurity.org>, Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>, Pawel Jakub Dawidek <pjd@freebsd.org> Subject: Re: kern/93942: panic: ufs_dirbad: bad dir Date: Fri, 3 Mar 2006 03:51:45 +0000 (GMT) On Thu, 2 Mar 2006, Yarema wrote: > options UFS_EXTATTR > options UFS_EXTATTR_AUTOSTART If you disable just UFS_EXTATTR_AUTOSTART, does the panic go away? The autostart routine relies on reading directory data (or at least, performing lookups) during the mount process. While it shouldn't be running on UFS2, it could be that it is, and if something has changed in the mount process so that reading directories that early is no longer functional, it could be that this causes an incorrect reporting of on-disk corruption (i.e., it could be a data structure initialization problem or the like). Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603030350.k233o6LF000920>