From: hanasaki <hanasaki@hanaden.com>
To: reiserfs-list@namesys.com
Subject: Re: --rebuild-tree always finds errors --check is ok
Date: Fri, 07 Jan 2005 18:44:06 -0600 [thread overview]
Message-ID: <41DF2CD6.7040800@hanaden.com> (raw)
In-Reply-To: <200501072343.08374.vitaly@namesys.com>
Could you outline exactly what takes place on a rebuild-tree?
I was under the incorrect assumption that if a rebuild-tree is 100%
successful then the FS is ok and a subsequent rebuild-tree will have
nothing to fix/report. .....
Vitaly Fertman wrote:
> On Tuesday 04 January 2005 20:25, hanasaki wrote:
>
>>Version of reiserfsk
>>======================
>>== From debian sarge
>>/sbin/reiserfsck -V
>>reiserfsck 3.6.19 (2003 www.namesys.com)
>>== also used the version in knoppix 3.7 with similar results
>>
>>the output of two consecutive runs of --rebuild-tree on the same
>>unmounted partition are attached. Below is the diff
>
>
> rebuild-tree finds some blocks that looks like reiserfs formatted
> blocks for the first sight whereas they are not and just belongs to
> some file bodies. The consistency check reveals no valid metadata
> in them, so they are considered as not valid reiserfs formatted blocks
> and left not modified on disk. This is why the second run of rebuild-tree
> finds them again and tries to do all the stuff again.
>
next prev parent reply other threads:[~2005-01-08 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-01 21:55 --rebuild-tree always finds errors --check is ok hanasaki
2005-01-04 14:30 ` Vladimir Saveliev
2005-01-04 17:25 ` hanasaki
2005-01-06 12:06 ` Vladimir Saveliev
2005-01-07 20:43 ` Vitaly Fertman
2005-01-08 0:44 ` hanasaki [this message]
2005-01-10 12:50 ` Vitaly Fertman
-- strict thread matches above, loose matches on Subject: below --
2004-12-31 5:35 hanasaki
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=41DF2CD6.7040800@hanaden.com \
--to=hanasaki@hanaden.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.