From: Oleg Drokin <green@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Thorsten Mauch <mauch@imkenberg.de>,
"'reiserfs-list@namesys.com'" <reiserfs-list@namesys.com>
Subject: Re: rebuild fs
Date: Tue, 5 Aug 2003 17:17:23 +0400 [thread overview]
Message-ID: <20030805131723.GH13689@namesys.com> (raw)
In-Reply-To: <3F2FA997.20101@namesys.com>
Hello!
On Tue, Aug 05, 2003 at 04:56:55PM +0400, Hans Reiser wrote:
> >>rephrase that as, use 3.6.11, if it still fails, tell us, the segfault
> >>will at least be fixed regardless of whether fsck has enough data to do
> >>its job.
> >But it was not failing on the IDE drive anyway.
> I don't understand the relevance of your statement to mine.
Since after transferring image to IDE made reiserfsck to not fail (and it failed on raid5 due to raid errors,
I think), your "if it still fails" statement was not adequate.
Current problem is that not everything is restored and some important files were lost.
Now, I know that recently we introduced some serious changes in reiserfsck and now
if the block have some slight corruption, it is not immediately discarded, but fsck actually
tries to extract some useful data out of it if it think this is really reiserfs metadata block.
That's why newer reiserfsck might achieve better results.
Bye,
Oleg
next prev parent reply other threads:[~2003-08-05 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 10:02 rebuild fs Thorsten Mauch
2003-08-05 10:45 ` Oleg Drokin
2003-08-05 12:28 ` Hans Reiser
2003-08-05 12:54 ` Oleg Drokin
2003-08-05 12:56 ` Hans Reiser
2003-08-05 13:17 ` Oleg Drokin [this message]
2003-08-05 13:28 ` Hans Reiser
2003-08-05 13:35 ` Oleg Drokin
2003-08-05 13:40 ` Hans Reiser
2003-08-05 14:19 ` Vitaly Fertman
2003-08-05 15:09 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2003-08-05 13:06 Thorsten Mauch
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=20030805131723.GH13689@namesys.com \
--to=green@namesys.com \
--cc=mauch@imkenberg.de \
--cc=reiser@namesys.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.