From owner-freebsd-bugs@FreeBSD.ORG Fri Mar 3 03:50:06 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E074616A422 for ; Fri, 3 Mar 2006 03:50:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61A5343D49 for ; Fri, 3 Mar 2006 03:50:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k233o65f000921 for ; Fri, 3 Mar 2006 03:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k233o6LF000920; Fri, 3 Mar 2006 03:50:06 GMT (envelope-from gnats) Date: Fri, 3 Mar 2006 03:50:06 GMT Message-Id: <200603030350.k233o6LF000920@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Robert Watson Cc: Subject: Re: kern/93942: panic: ufs_dirbad: bad dir X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Watson List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2006 03:50:07 -0000 The following reply was made to PR kern/93942; it has been noted by GNATS. From: Robert Watson To: Yarema Cc: FreeBSD-gnats-submit@freebsd.org, FreeBSD-current@freebsd.org, David Rhodus , Dennis Koegel , Martin Machacek , Kris Kennaway , Dmitry Pryanishnikov , Pawel Jakub Dawidek 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