From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Oleg Drokin <green@namesys.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
Hans Reiser <reiser@namesys.com>,
linux-kernel@vger.kernel.org, Nikita Danilov <god@namesys.com>
Subject: Re: Reiser3/4 & Ext2/3 was: First impressions of reiserfs4
Date: Fri, 12 Sep 2003 00:50:08 +0200 [thread overview]
Message-ID: <20030912005007.B11566@bitwizard.nl> (raw)
In-Reply-To: <20030911172740.GK29357@namesys.com>
On Thu, Sep 11, 2003 at 09:27:40PM +0400, Oleg Drokin wrote:
> > > as are superblock, journal and journal header.
> > How many superblocks are there in reiser3? Also, the bitmap locations are
>
> One superblock.
As we've experienced that it's possible to lose the one-and-only
superblock, I would recommend that you build a backup superblock
in the future. Of course you're going to argue that some parameters
constantly change in the superblock so that it would mean a performance
penalty to have two of them. Well, the backup superblock should
be marked and used as such: It will allow a more "easy" recovery
of the filesystem parameters, should the primary be "gone", but
it should not interfere with "normal operation". So, feel free to
only update it once every ten minutes or so. Or just initialize
it and only write it when the fs is unmouted. Or don't update it
at all. But no backup superblock, is just plain wrong.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
**** "Linux is like a wigwam - no windows, no gates, apache inside!" ****
next prev parent reply other threads:[~2003-09-11 22:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 11:33 First impressions of reiserfs4 Erik Hensema
2003-08-30 17:06 ` Hans Reiser
2003-08-31 17:14 ` Rogier Wolff
2003-09-08 8:12 ` Oleg Drokin
2003-09-08 8:56 ` Rogier Wolff
2003-09-08 9:08 ` Oleg Drokin
2003-09-08 9:33 ` Rogier Wolff
2003-09-08 9:48 ` Oleg Drokin
2003-09-08 10:05 ` Rogier Wolff
2003-09-08 10:17 ` Oleg Drokin
2003-09-08 12:59 ` Herbert Poetzl
2003-09-08 22:24 ` Mike Fedyk
2003-09-09 7:04 ` Oleg Drokin
2003-09-09 19:10 ` Mike Fedyk
2003-09-11 10:29 ` Oleg Drokin
2003-09-11 17:15 ` Reiser3/4 & Ext2/3 was: " Mike Fedyk
2003-09-11 17:27 ` Oleg Drokin
2003-09-11 22:50 ` Rogier Wolff [this message]
2003-09-12 1:20 ` Bernd Eckenfels
2003-09-12 4:48 ` Mike Fedyk
2003-10-01 21:06 ` Bernd Eckenfels
2003-10-02 6:36 ` Hans Reiser
2003-09-12 1:17 ` Bernd Eckenfels
2003-09-08 20:11 ` Andreas Dilger
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=20030912005007.B11566@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=god@namesys.com \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).