From: Oleg Drokin <green@namesys.com>
To: "John P. New" <jnew@hazelden.ca>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Procedure to recover a bad superblock
Date: Tue, 19 Aug 2003 09:41:34 +0400 [thread overview]
Message-ID: <20030819054134.GH10536@namesys.com> (raw)
In-Reply-To: <1061216567.3562.50.camel@headoffice.hazelden.ca>
Hello!
On Mon, Aug 18, 2003 at 10:22:47AM -0400, John P. New wrote:
[...]
> Set flags in SB:
> Is this ok ? (y/n)[n]: y
> The fs may still be unconsistent. Run reiserfsck --check.
> And then I ran reiserfsck --check --logfile /root/rfscheck.log /dev/md1
> and got (edited):
[...]
> Bad root block 0. (--rebuild-tree did not complete)
> Aborted (core dumped)
> Now what? Is it time for a --rebuild-tree, or are we past that because
> of the 'Bad root block 0. (--rebuild-tree did not complete)' error?
Well, since your superblock was completely destroyed, we no longer know where rootblock is.
So you need to run reiserfsck --rebuild-tree now
Bye,
Oleg
prev parent reply other threads:[~2003-08-19 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 14:52 Procedure to recover a bad superblock John P. New
2003-08-18 6:19 ` Oleg Drokin
2003-08-18 11:43 ` John P. New
2003-08-18 13:33 ` Oleg Drokin
2003-08-18 14:22 ` John P. New
2003-08-19 5:41 ` Oleg Drokin [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=20030819054134.GH10536@namesys.com \
--to=green@namesys.com \
--cc=jnew@hazelden.ca \
--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.