Re: ReiserFS phenomenon with 2.4.2 ac24/ac12

[Chris Mason <mason@suse.com>]

On Tuesday, March 27, 2001 09:50:17 AM -0800 Christoph Lameter
<christoph@lameter.com> wrote:
>> 
>> Ok, notice how entry 2 and 3 are the same file name?  That is a big part
>> of your problem, and it should never happen with the normal kernel code.
>> The two lines that show up as (BROKEN) mean their hash values are
>> incorrect.
>> 
>> So, were there errors present before you ran reiserfsck -x?  Had you run
>> any version of reiserfsck (with -x or --rebuild-tree) before that?
> 
> The problems were present before I ran reiserfsck. I never ran
> --rebuild-tree

Just to make sure I understand, you had the exact same errors before
running fsck?  Same files could not be deleted?

> 
>> I'm guessing these problems were caused by reiserfsck, things caused by
>> kernel bug would tend towards much more random errors.  The solution will
>> probably be an upgrade to the latest fsck version, but I'd like to make
>> sure we've got the problem nailed down.
> 
> I think this is a problem with the reiserfs code in the kernel. I never
> ran reiserfsck before this problem surfaced. The problem arose in the
> netscape cache directory with lots of small files. Guess the tail handling
> is not that stable yet?

I wish I could blame it on the tail code ;-)  None of the bugs fixed there
would have caused this, and they should be completely unrelated.  I'll try
some tests in oom situations to try and reproduce.  It could also be caused
by hashing errors.  If you formatted with r5 hash, was the partition ever
incorrectly detected as tea hash?

> 
> How do I get rid of the /a/yy directory now?

With fsck.  I'll grab the latest today and make sure it can fix this bug.
Until then, mv /a/yy /a/yy.broken and mkdir /a/yy.

-chris