Re: panic: /e: bad dir ino 584288256 at offset 0: null entry

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

Should this be moved to trech-kern maybe?

>>> My guess is that something is wrong on your filesystem that fsck
>>> does not check for.
>> What sort of things does fsck not check for?
> Probably there are several.

Probably!

If you reallyk care, go through the FFS code and look at every panic to
see (a) if it's an on-disk error (as opposed to an in-core
can't-happen) and (b) whether fsck would have caught that condition.
When I was doing the program that became resize_ffs I ran into an
example; it's gone as of 5.2, so presumably gone in current as well,
but I think it's too much to hope there are no more.

Indeed, this thread indicates that there is some condition (a "null
entry", which appears to mean an entry with zero d_reclen) that the
kernel thinks worth panic()ing over but that fsck doesn't seem to mind.

If my reading is right, and it _is_ an entry with zero d_reclen, IMO
it's a bug in fsck that it doesn't catch it.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse%rodents-montreal.org@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B