public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Tue, 27 Mar 2001 09:34:56 -0500	[thread overview]
Message-ID: <206950000.985703696@tiny> (raw)
In-Reply-To: <Pine.LNX.4.21.0103261841240.31038-100000@home.lameter.com>



On Monday, March 26, 2001 06:57:37 PM -0800 Christoph Lameter
<christoph@lameter.com> wrote:

> On Mon, 26 Mar 2001, Chris Mason wrote:
>> On Monday, March 26, 2001 03:21:29 PM -0800 Christoph Lameter
>> > On Mon, 26 Mar 2001, Chris Mason wrote:
>> >> On Saturday, March 24, 2001 11:56:08 AM -0800 Christoph Lameter
>> >> <christoph@lameter.com> wrote:
>> >> > I got a directory /a/yy that I tried to erase with rm -rf /a/yy.
>> >> > 
>> >> > rm hangs...
>> >> > 
>> >> > ls gives the following output:
>> >> > 
>> >> > ls: /a/yy/cache3A0F94EA0A00557.html: No such file or directory
>> >> > ls: /a/yy/cache3A0F94EA0A00557.html: No such file or directory
>> >> > ls: /a/yy/cache3A8CCC6A0490B05.gifcache393C2B6A2CD2DF1.crumb: No
>> >> > such file or directory
>> >> > ls: /a/yy/cache3A0F94EA0A00557.html: No such file or directory
>> >> > ls: /a/yy/cache3A0F94EA0A00557.html: No such file or directory
>> >> > ls: /a/yy/cache3A8CCC6A0490B05.gifcache393C2B6A2CD2DF1.crumb: No
>> >> > such file or directory
>> >> > 
>> >> > 
> output of reiserfsck:
> 
> grow_id_map: objectid map expanded: used 1024, 1 blocks

These are harmless and should have been removed from fsck forever ago.

> bad_leaf: block 9454 has invalid item 4: 1928 5204 0x1 DIR, len 184,

This is probably the cause of the errors.  hopefully /a is inode number
1928 and /a/yy is inode number 5204 ( you can check with ls -i ).  Please
send me (privately) the output of debugreiserfs -b 9454, and we'll figure
out the best way to fix it.

> check_semantic_tree: hash mismatch detected (cache3A0F94EA0A00557.html)
> check_semantic_tree: name "cache3A0F94EA0A00557.html" in directory 1928
> 5204 points to nowhere check_semantic_tree: hash mismatch detected
> (cache3A8CCC6A0490B05.gifcache393C2B6A2CD2DF1.crumb) check_semantic_tree:
> name "cache3A8CCC6A0490B05.gifcache393C2B6A2CD2DF1.crumb" in directory
> 1928 5204 points to nowhere

And these are in the bad directory mentioned above.

-chris





  reply	other threads:[~2001-03-27 14:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <174740000.985659658@tiny>
2001-03-27  2:57 ` ReiserFS phenomenon with 2.4.2 ac24/ac12 Christoph Lameter
2001-03-27 14:34   ` Chris Mason [this message]
2001-03-27 16:21     ` Christoph Lameter
2001-03-27 17:08       ` Chris Mason
2001-03-27 17:50         ` Christoph Lameter
2001-03-27 18:02           ` Chris Mason
2001-03-27 19:14             ` Christoph Lameter
2001-03-27 19:20               ` Chris Mason
2001-03-27 21:44                 ` Christoph Lameter
     [not found] <87200000.985628791@tiny>
2001-03-26 23:21 ` Christoph Lameter
2001-03-24 19:56 Christoph Lameter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=206950000.985703696@tiny \
    --to=mason@suse.com \
    --cc=christoph@lameter.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox