From: Oleg Drokin <green@namesys.com>
To: "Ing. Davide Imbeni" <davide.imbeni@tei.ericsson.se>,
davide.imbeni@tiscali.it
Cc: reiserfs-list@namesys.com
Subject: Re: Mount fails after reiserfsck --rebuild-tree failure
Date: Fri, 20 Jun 2003 16:34:50 +0400 [thread overview]
Message-ID: <20030620123450.GB24875@namesys.com> (raw)
In-Reply-To: <FCEDLNJPOJKGBCPDLKPGGEFMCBAA.g_luppi@brokerstudio.it>
Hello!
On Thu, Jun 19, 2003 at 09:11:29PM +0200, Giuliano Luppi wrote:
> Now I know the problems are (a lot of) bad blocks.
> I would like to
> 1. re-enable mounting the partition, in order to recover some of the data I
> still have there (I know, I should backup more often? :-( )
This is not possible to "reenable" it.
> 2. possibly fix the badblocks (as you describe in section 38 of the FAQ), in
> order to bring up the system until new hard disks are ready.
This is not possible in your case, I'd say.
What you can do - is you can copy entire block device to a file/another device
and run rebuild-tree there. Use dd_rescue for copying.
> The main question is: how can I undo the setting of root inode to 0?
There is no such way, if you do not know what was the location of root node.
> Is there a good way for dealing with faulty hardware with reiserfs?
There is no good (reliable) way of dealing with faulty hardware with software, except avoiding
faulty hardware at all costs, I believe.
Bye,
Oleg
next prev parent reply other threads:[~2003-06-20 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 19:11 Mount fails after reiserfsck --rebuild-tree failure Giuliano Luppi
2003-06-20 12:34 ` Oleg Drokin [this message]
2003-06-23 9:28 ` Davide Imbeni
2003-06-23 9:11 ` Alexander Lyamin
-- strict thread matches above, loose matches on Subject: below --
2004-03-17 17:43 KAA
2004-03-17 18:00 ` jlewis
2004-03-17 21:31 ` Vitaly Fertman
2004-03-17 21:34 ` 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=20030620123450.GB24875@namesys.com \
--to=green@namesys.com \
--cc=davide.imbeni@tei.ericsson.se \
--cc=davide.imbeni@tiscali.it \
--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.