From: "Jakub Ambrożewicz" <ja@vigor.com.pl>
To: reiserfs-list@namesys.com
Subject: Re: superblock problem
Date: Wed, 26 Jun 2002 15:30:02 +0200 [thread overview]
Message-ID: <3D19C1DA.3070508@vigor.com.pl> (raw)
In-Reply-To: 3D19A3ED.6040201@vigor.com.pl
On 6/26/02 1:22 PM, Jakub Ambro¿ewicz wrote:
> So i thought maybe i used wrong version and tried
> all of the options, still no result. And now i stuck
I forgot to mention that two upper version options
of --rebuild-sb (ie 3.6.x and 3.5.9) resulted in
superblock beeing written at block 16. Two lower versions
wrote sb at block 2. But kernel still expected them to be
at block 8.
JA
prev parent reply other threads:[~2002-06-26 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 11:22 superblock problem Jakub Ambrożewicz
2002-06-26 13:30 ` Jakub Ambrożewicz [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=3D19C1DA.3070508@vigor.com.pl \
--to=ja@vigor.com.pl \
--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.