All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: alistair@inrevo.com
Cc: reiserfs-list@namesys.com
Subject: Re: Bad block 0 error
Date: Mon, 21 Jun 2004 16:45:00 +0400	[thread overview]
Message-ID: <40D6D84C.5080408@namesys.com> (raw)
In-Reply-To: <35523.170.148.10.46.1087819828.squirrel@170.148.10.46>

Hello

Alistair McDonald wrote:
> Hello, Vladimir
> 
> Thanks for replying.
> I have run with --rebuild-tree, and the results are below. Thanks for any
> further help you can offer.
> 
> 
>>>A little googling suggsted using the debugreiserfs command, but the
>>>output
>>>seems normal to me:
>>>
>>
>>No, it is not. You see: tree height is supposed to be not more than 5.
>>You have 65535. Root block is block 0 which should never happen. So, you
>>have to run reiserfsck --rebuild-tree
> 
> 
> ================================ reiserfsck --rebuild tree output starts
> Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
> Replaying journal..
> Reiserfs journal '/dev/md0' in blocks [18..8211]: 0 transactions replayed
> ###########
> reiserfsck --rebuild-tree started at Mon Jun 21 13:02:36 2004
> ###########
> 
> Pass 0:
> ####### Pass 0 #######
> Loading on-disk bitmap .. ok, 10081 blocks marked used
> Skipping 10081 blocks (super block, journal, bitmaps) 0 blocks will be read
> 
> Could not find a hash in use. Using "r5"
>         "r5" hash is selected
> Flushing..finished
>         Read blocks (but not data blocks) 0
>                 Leaves among those 0
>                 Objectids found 2
> 
> Pass 1 (will try to insert 0 leaves):
> ####### Pass 1 #######
> Looking for allocable blocks .. finished
> 
> Flushing..finished
>         0 leaves read
>                 0 inserted
> ####### Pass 2 #######
> Flushing..finished
> 
> 
> No reiserfs metadata found.  If you are sure that you had the reiserfs
> on this partition,  then the start  of the partition  might be changed

Lets try to see if there are reiserfs metadata on /dev/md0:

echo "\n" | 3.6.17/debugreiserfs -k -S -q /dev/md0 | head 10000

It should output something like:
block 17775 is reiserfs leaf node

If you do not see such lines - reiserfsck can not do anything with that 
device.

please also run
debugreiserfs -m /dev/md0 > md0.bitmap
and send us md0.bitmap


  reply	other threads:[~2004-06-21 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21  9:27 Bad block 0 error Alistair McDonald
2004-06-21 11:50 ` Vladimir V. Saveliev
2004-06-21 12:10   ` Alistair McDonald
2004-06-21 12:45     ` Vladimir V. Saveliev [this message]
2004-06-21 15:19       ` Alistair McDonald
2004-06-21 15:41         ` 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=40D6D84C.5080408@namesys.com \
    --to=vs@namesys.com \
    --cc=alistair@inrevo.com \
    --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.