From: Oleg Drokin <green@namesys.com>
To: Peter Herklotz <linux@pch-edv.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfsck segmentation fault
Date: Thu, 22 Aug 2002 17:06:11 +0400 [thread overview]
Message-ID: <20020822170611.B6550@namesys.com> (raw)
In-Reply-To: <347248875.20020822135632@pch-edv.com>
Hello!
On Thu, Aug 22, 2002 at 01:56:32PM +0200, Peter Herklotz wrote:
> thanks for the advice, reiserfsck (3.6.3) is working heavily now - lets hope
> it can rebuild the content of the partition. But another question
> arises for me: As I pointed out in my first posting, I had to do a
> "reiserfsck --rebuild-sb" first before the partition was even recognized
> as an reiserfs one. As I said, I wasn't sure which version of the fs I
> had. How dangerous is it to choose a wrong "3.5.x"-version at that
> point? The only thing that I am sure of is that it wasn't a 3.6
> version.
wrong 3.5 version is dangerous because they have different bitmaps layout.
Bye,
Oleg
prev parent reply other threads:[~2002-08-22 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 11:10 reiserfsck segmentation fault Linux PCH EDV
2002-08-22 11:14 ` Oleg Drokin
2002-08-22 11:56 ` Re[2]: " Peter Herklotz
2002-08-22 13:06 ` 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=20020822170611.B6550@namesys.com \
--to=green@namesys.com \
--cc=linux@pch-edv.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.