From: Marc Schmitt <mschmitt@inf.ethz.ch>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Vitaly Fertman <vitaly@namesys.com>,
ReiserFS-List <reiserfs-list@namesys.com>
Subject: Re: Bad root block 0. (--rebuild-tree did not complete)
Date: Tue, 02 Dec 2003 21:53:50 +0100 [thread overview]
Message-ID: <3FCCFBDE.50909@inf.ethz.ch> (raw)
In-Reply-To: <3FCCF88D.5050006@gmx.net>
Hi Carl-Daniel,
Carl-Daniel Hailfinger wrote:
>Marc Schmitt wrote:
>
>
>>Hi Vitaly,
>>
>>Thanks for the fast answer.
>>
>>Vitaly Fertman wrote:
>>
>>
>>
>>>Hi Marc,
>>>
>>>
>>>
>[...]
>
>
>>>Would you run debugreiserfs -p /dev/problem_device | bzip2 -c >
>>>metadata.bz2
>>>and make it available for downloading. I will debug the problem
>>>locally then.
>>>
>>>
>>>
>>It is running now. I'll make the file metadata.bz2 available for
>>downloading asap. ETA is 10h, right, if the `reiserfsck --rebuild-tree`
>>took 10h before it segfaulted?
>>
>>
>
>No. More like a few minutes for disk accesses and some time for
>compressing the result. The command is of the "read all metadata and dump
>it without any additional checks whatsoever" variety.
>
Hmm, it's running for 15' now and it does not look like it's going to
finish soon:
debugreiserfs 3.6.11 (2003 www.namesys.com)
Loading on-disk bitmap .. 162980857 bits set - done
super block..ok
bitmaps..(5396).. ok
journal (from 18 to 8210)..ok
Super block, bitmaps, journal - 13590 blocks - done, 162967267 blocks left
0% left 161169318,
1250 /sec
The file metadata.bz2 is still growing. The 1250 /sec increased slowly
during fsck and went up to 6000 /sec towards the end. At the current
pace, it would take 36h...
Greetz
Marc
next prev parent reply other threads:[~2003-12-02 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 19:28 Bad root block 0. (--rebuild-tree did not complete) Marc Schmitt
2003-12-02 20:06 ` Vitaly Fertman
2003-12-02 20:28 ` Marc Schmitt
2003-12-02 20:39 ` Carl-Daniel Hailfinger
2003-12-02 20:53 ` Marc Schmitt [this message]
2003-12-02 21:17 ` Carl-Daniel Hailfinger
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=3FCCFBDE.50909@inf.ethz.ch \
--to=mschmitt@inf.ethz.ch \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.