Date: Tue, 27 Mar 2001 12:08:37 -0500
From: Chris Mason <mason@suse.com>
To: Christoph Lameter <christoph@lameter.com>
cc: linux-kernel@vger.kernel.org
Subject: Re: ReiserFS phenomenon with 2.4.2 ac24/ac12
Message-ID: <284560000.985712917@tiny>
In-Reply-To: <Pine.LNX.4.21.0103270820190.6242-100000@home.lameter.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org


On Tuesday, March 27, 2001 08:21:07 AM -0800 Christoph Lameter
<christoph@lameter.com> wrote:

>  
> <-------------debugreiserfs, 2000------------->
> reiserfsprogs 3.x.0h
> 9454 is free in true bitmap
>  
> ===================================================================
> LEAF NODE (9454) contains level=1, nr_items=11, free_space=16 rdkey
> -------------------------------------------------------------------------
> ------ |  3|1928 5204 0x0 SD, len 44, entry count 65535, fsck need 0,
> format new| (NEW SD), mode d---------, size 96, nlink 2, mtime 03/23/2001
> 20:49:37
> -------------------------------------------------------------------------
> ------ |  4|1928 5204 0x1 DIR, len 184, entry count 5, fsck need 0,
> format old| ###: Name                     length    Object key
> Hash     Gen number
>   0: ".                        "(  1)   1928           5204           0
> 1, loc b0,  state 4 ()
>   1: "..                       "(  2)      1              2           0
> 2, loc a8,  state 4 ()
>   2: "cache3A0F94EA0A00557.html"( 25)   5204           5334  1942043776
> 0, loc 88,  state 4 ()
>   3: "cache3A0F94EA0A00557.html"( -6) 263760           5334        5248
> 86, loc 88,  state 4 (BROKEN)
>   4: "cache3A8CCC6A0490B05.gifcache393C2B6A2CD2DF1.crumb"( 50) 263760
> 64136        5248   86, loc 50,  state 4 (BROKEN)

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?

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.

-chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/