All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Malinovich <demonbane@the-love-shack.net>
To: reiserfs-list@namesys.com
Subject: Re: reiserfsck "block is in the tree already" error
Date: 21 Mar 2003 20:44:50 -0600	[thread overview]
Message-ID: <1048301090.925.1.camel@Thief> (raw)
In-Reply-To: <200303212014.29775.vitaly@namesys.com>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

On Fri, 2003-03-21 at 11:14, Vitaly Fertman wrote:
> Hi, 
> 
> On Friday 21 March 2003 20:05, Alex Malinovich wrote:
> > I've been trying to rebuild the tree on a reiserfs partition that seems
> > to have gotten corrupted during a resize operation. Unfortunately, I've
> > gone from having one or two directories not accessible to having the
> > whole partition not accessible now. Everything seems to go ok until pass
> > 2. At this point I start getting this error:
> >
> > "do_pass_2: The block (4901823) is in the tree already. Should not
> > happen."
> 
> It seems that reiserfsck was built on another computer, which has some 
> other libs version, not statically. Would you try to rebuild it and try 
> again.

I just downloaded the source and built it and it worked! Thank you VERY
much!

-- 
Alex Malinovich
Support Free Software, delete your Windows partition TODAY!
Encrypted mail preferred. You can get my public key from any of the
pgp.net keyservers. Key ID: A6D24837

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-03-22  2:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 17:05 reiserfsck "block is in the tree already" error Alex Malinovich
2003-03-21 17:14 ` Vitaly Fertman
2003-03-22  2:44   ` Alex Malinovich [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=1048301090.925.1.camel@Thief \
    --to=demonbane@the-love-shack.net \
    --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.