From: Vitaly Fertman <vitaly@namesys.com>
To: mharnois@cpinternet.com, reiserfs-list@namesys.com
Subject: Re: rebuild-tree fails in pass 2
Date: Thu, 15 Jan 2004 16:07:37 +0300 [thread overview]
Message-ID: <200401151601.25022.vitaly@namesys.com> (raw)
In-Reply-To: <400689ed.42cd.0@cpinternet.com>
Hello,
On Thursday 15 January 2004 15:39, Michael Harnois wrote:
> I am running a 2.6.1 kernel pulled from bk yesterday and using
> reiserfsprogs-3.6.11. Something happened after I rebooted that
> caused filesystem corruption which instructed me to run
> rebuild-tree. But it will not run to completion. During pass 2
> it fails with
> Assertion `*first < bm->bm_bit_size' failed
>
> Any ideas?
Looks like a broken hardware (RAM?) or probably you build the
progs not statically on one computer and then run reiserfsck on
another one (with another glibc installed). Would you check it?
--
Thanks,
Vitaly Fertman
next prev parent reply other threads:[~2004-01-15 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 12:39 rebuild-tree fails in pass 2 Michael Harnois
2004-01-15 13:07 ` Vitaly Fertman [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 13:17 Michael Harnois
2004-01-15 13:30 ` Vitaly Fertman
2004-01-15 18:58 ` Vitaly Fertman
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=200401151601.25022.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=mharnois@cpinternet.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.