From owner-freebsd-current@FreeBSD.ORG Fri Mar 3 03:47:53 2006 Return-Path: X-Original-To: FreeBSD-current@freebsd.org Delivered-To: FreeBSD-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41FBC16A420; Fri, 3 Mar 2006 03:47:53 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7079143D6A; Fri, 3 Mar 2006 03:47:24 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id F148B46C1C; Thu, 2 Mar 2006 22:46:51 -0500 (EST) Date: Fri, 3 Mar 2006 03:51:45 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Yarema In-Reply-To: Message-ID: <20060303034932.V58513@fledge.watson.org> References: <20060228195343.GA85313@xor.obsecurity.org> <3BD79FAD83E2122EC1644386@ramen.coolrat.org> <20060301201937.GA29208@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: David Rhodus , Pawel Jakub Dawidek , Dennis Koegel , FreeBSD-current@freebsd.org, Martin Machacek , Kris Kennaway , Dmitry Pryanishnikov , FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/93942: panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2006 03:47:53 -0000 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