All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: grossnik.mailinglists@hispeed.ch
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfsck (3.6.19) --rebuild-tree failed
Date: Fri, 8 Sep 2006 15:22:40 +0400	[thread overview]
Message-ID: <200609081522.40534.vs@namesys.com> (raw)
In-Reply-To: <200609081130.k88BUpi3004823@smtp.hispeed.ch>

Hello

On Friday 08 September 2006 15:30, grossnik.mailinglists@hispeed.ch wrote:
> Hi Vladimir
>
> >ok, all bad blocks are used. Lets try to find what they are used for:
> >cat /root/hda3.bad | debugreiserfs -x /dev/hda3
>
> # cat /root/hda3.bad | ./debugreiserfs -x /dev/hda3 > /root/tmp.txt 2>&1
> =>
>
> debugreiserfs 3.6.19.3 (2003 www.namesys.com)
>
> list of 21 block numbers is read
> /0

ah, sorry, I forgot that you ran reiserfsck --rebuild-tree and that did not 
complete. debureiserfs -x will not help.

I will try to reproduce your problem here and debug it.

Btw, did reiserfstune say you something like the below?

reiserfstune -B list2 /dev/hda2
reiserfstune: Bad block 32793 is used already in reiserfs tree. To mark it as 
a bad block use reiserfsck
--fix-fixable with -B option.




> block #0 has wrong level 0, has to be 65534
> Number of unresolved block numbers: 21
>
>
>
> Kind Regards
> Bruno

  reply	other threads:[~2006-09-08 11:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 11:30 Re: reiserfsck (3.6.19) --rebuild-tree failed grossnik.mailinglists
2006-09-08 11:22 ` Vladimir V. Saveliev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-08 14:42 grossnik.mailinglists
2006-09-09 15:25 ` Michael Weissenbacher
2006-09-08 12:04 grossnik.mailinglists
2006-09-08 12:48 ` Vladimir V. Saveliev
2006-09-08 10:51 grossnik.mailinglists
2006-09-08 10:48 ` Vladimir V. Saveliev
2006-09-08  9:51 grossnik.mailinglists
2006-09-08 10:05 ` Vladimir V. Saveliev

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=200609081522.40534.vs@namesys.com \
    --to=vs@namesys.com \
    --cc=grossnik.mailinglists@hispeed.ch \
    --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.