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 19:41:25 +0400 [thread overview]
Message-ID: <40D701A5.9030508@namesys.com> (raw)
In-Reply-To: <55895.170.148.92.18.1087831146.squirrel@170.148.92.18>
Hello
Alistair McDonald wrote:
> Hi,
>
>
>>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.
>
>
> Well, it took a *long, long* time, but here are the results (the command
> changed slightly):
>
> # echo "\n" | debugreiserfs -k -S -q /dev/md0 | head -10000
> head: `-10000' option is obsolete; use `-n 10000' since this will be
> removed in
> the future
> debugreiserfs 3.6.17 (2003 www.namesys.com)
>
> Whole device (61277904 blocks) is to be scanned
> looking for ([0 0])
> 0%...\.20%....40%....60%..
> Log file 'scan.log' is opened
> What key do you want to find: dirid?objectid?block 16 is reiserfs super block
> block 18 is journal descriptor
> block 19 is reiserfs super block
> block 21 is journal descriptor
> block 22 is reiserfs super block
> block 24 is journal descriptor
> block 25 is reiserfs super block
> altair root # \
>
>
>
>>please also run
>>debugreiserfs -m /dev/md0 > md0.bitmap
>>and send us md0.bitmap
>>
>
>
> I will send the md0.bitmap directly to you (not to the list) once that
> command has completed.
>
Hmm, I am afraid that I will have to disappoint you. /dev/md0 does not
contain reiserfs metadata blocks. Would you make sure once again that
you dd_rescue-ed broken reiserfs filesystem to /dev/md0?
> Many thanks,
>
> Alistair
>
>
>
prev parent reply other threads:[~2004-06-21 15:41 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
2004-06-21 15:19 ` Alistair McDonald
2004-06-21 15:41 ` Vladimir V. Saveliev [this message]
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=40D701A5.9030508@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.