From owner-freebsd-current  Tue Aug 21  9:34:29 2001
Delivered-To: freebsd-current@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by hub.freebsd.org (Postfix) with SMTP id 4A9DD37B407
	for <freebsd-current@FreeBSD.ORG>; Tue, 21 Aug 2001 09:34:20 -0700 (PDT)
	(envelope-from iedowse@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa71132@salmon>; 21 Aug 2001 17:34:19 +0100 (BST)
To: Ollivier Robert <roberto@keltia.freenix.fr>
Cc: FreeBSD Current Users' list <freebsd-current@FreeBSD.ORG>
Subject: Re: Panic with latest current/UFS_DIRHASH 
In-Reply-To: Your message of "Tue, 21 Aug 2001 17:15:10 +0200."
             <20010821171510.A75116@tara.freenix.org> 
Date: Tue, 21 Aug 2001 17:34:16 +0100
From: Ian Dowse <iedowse@maths.tcd.ie>
Message-ID:  <200108211734.aa71132@salmon.maths.tcd.ie>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

In message <20010821171510.A75116@tara.freenix.org>, Ollivier Robert writes:
>
>The interesting thing is that I also get that with my old 17th Jul.
>kernel... except that the panic message is 
>
>"ufsdirhash_checkblock: bad dir inode"
>
>It is always in the following part of installworld:

That's interesting - the "bad dir inode" bit in particular. I'll
look into this in more detail later. My first guess is that there
is a logic flaw in the dirhash code that only triggers when dirhash
comes across a directory entry that has had its inode zeroed by
fsck.

The kernel filsystem code only ever places unused directory entries
at the start of a directory block (free space that is not at the
start of a block is merged into an exesting entry). However, fsck
can mark any entry as unused, resulting in the unfortunate situation
that fsck can put the filesystem into a state that cannot be produced
by any combination of kernel filesystem operations. That introduces
quite some potential for obscure bugs that only occur after an fsck
run...

Ian

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message