From owner-freebsd-current@FreeBSD.ORG  Fri Oct 14 19:40:47 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 3E76C16A41F;
	Fri, 14 Oct 2005 19:40:47 +0000 (GMT)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CE61143D70;
	Fri, 14 Oct 2005 19:40:46 +0000 (GMT)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com (localhost [127.0.0.1])
	by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id j9EJeYoY024833;
	Fri, 14 Oct 2005 12:40:34 -0700 (PDT)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.13.4/8.13.4/Submit) id j9EJeYsn024832;
	Fri, 14 Oct 2005 12:40:34 -0700 (PDT)
Date: Fri, 14 Oct 2005 12:40:34 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <200510141940.j9EJeYsn024832@apollo.backplane.com>
To: obrien@freebsd.org
References: <20050926152952.GA1670@dragon.NUXI.org>
	<20050926160808.GB1649@dragon.NUXI.org>
Cc: freebsd-current@freebsd.org
Subject: Re: [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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Oct 2005 19:40:47 -0000


:Just got another one - uptime was about 10 minutes.  Is one of the recent
:changes to SU & FFS making this situation easier to trigger?
:
:-- 
:-- David  (obrien@FreeBSD.org)

    This is happening on DragonFly, too.  Three people (including me) have
    seen it.  All with different hardware/hard-disk configs.

    It definitely is not hardware.

    It does not seem to be related to a crash... it happens seemingly randomly,
    but often during heavy directory / filesystem use (e.g. pkgsrc builds).
    The one crash dump I've looked at very suspiciously shows the bad 
    buffer at filesystem block 12 (the first INDIRECT block).  The contents
    of the buffer looks like a random filesystem block rather then a directory
    block.

    I am going to commit Tor's patch and see if the bug reports go away.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>