All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Daniel Christiansen <christiansen@albion.edu>
Cc: reiserfs-list@namesys.com
Subject: Re: Error Code 255 and "Permission Denied"
Date: Mon, 6 May 2002 15:21:01 +0400	[thread overview]
Message-ID: <20020506152101.A904@namesys.com> (raw)
In-Reply-To: <scd52321.066@gwd.albion.edu>

Hello!

On Sun, May 05, 2002 at 12:18:28PM -0400, Daniel Christiansen wrote:

> The message in the logfile was"Node (8272) with wrong level (0) found in
> the tree (should be 1)." [There was also a message on the screen of
> "pass_through_tree: unable to read 2949119 block on device 0x4."]  The
> --fix-fixable option didn't seem to do anything.
> [Although, if I recall correctly, there was a message having to do with
> resizing that I didn't understand.]

Can you find out that message in your logs? It may be important one.

> I started to use the --rebuild-tree option but was dissuaded by the
> message about only using it if I was desperate.  Perhaps I need to take
> a deep breath and use this option.

Make sure to get latest reiserfsprogs (v3.x.1b) from namesys ftp site.

> Other indications of a problem:  I ran the dmesg program from /bin and
> got "Warning log replay starting on readonly filesystem" and lots of
> "i/o failure trying to find stat data" messages.

Your filesystem was corrupted by something. Do you have Windows on that box,
too?

> "kernel: is_tree_node: node level 0 does not match to the expected one 1
> kernel: vs-5150: search_by_key: invalid format found in block 8272.
> Fsck?"

This message confirms damaged blocks theory.

> I would appreciate any suggestions as to how fix my problem.

Get latest reiserfsprogs package and run reiserfsck --rebuild-tree.

Bye,
    Oleg

  reply	other threads:[~2002-05-06 11:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-05 16:18 Error Code 255 and "Permission Denied" Daniel Christiansen
2002-05-06 11:21 ` Oleg Drokin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-06 16:07 Daniel Christiansen
2002-05-06 18:06 ` Oleg Drokin
2002-05-06 19:12 Daniel Christiansen
2002-05-07  0:54 ` Manuel Krause
2002-05-07  1:53   ` Chris Mason
2002-05-07  5:12   ` Oleg Drokin

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=20020506152101.A904@namesys.com \
    --to=green@namesys.com \
    --cc=christiansen@albion.edu \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.