Date: Tue, 21 Aug 2001 17:34:16 +0100 From: Ian Dowse <iedowse@maths.tcd.ie> To: Ollivier Robert <roberto@keltia.freenix.fr> Cc: FreeBSD Current Users' list <freebsd-current@FreeBSD.ORG> Subject: Re: Panic with latest current/UFS_DIRHASH Message-ID: <200108211734.aa71132@salmon.maths.tcd.ie> In-Reply-To: Your message of "Tue, 21 Aug 2001 17:15:10 %2B0200." <20010821171510.A75116@tara.freenix.org>
index | next in thread | previous in thread | raw e-mail
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 messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108211734.aa71132>