From: Eric Sandeen <sandeen@sandeen.net>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: REVIEW: Change mkfs.xfs to set primary superblock inodes in ALL secondaries
Date: Wed, 03 Sep 2008 09:11:59 -0500 [thread overview]
Message-ID: <48BE9B2F.30606@sandeen.net> (raw)
In-Reply-To: <op.ugv794p63jf8g2@pc-bnaujok.melbourne.sgi.com>
Barry Naujok wrote:
> One peculiarity of mkfs.xfs that no-one has yet been able to explain
> to me is that all the secondary superblocks do not contain the
> primary superblock's root inode, realtime inodes and quota inodes.
>
> The root inode is stored in the middle and last AG as well to
> make things more unexpected.
>
> The following makes all the secondaries the same as the primary
> (other than the global counters).
Also looks good to me.
I've always wondered, too, if writing a single backup superblock in the
last sector(s) of the device at mkfs/growfs time might be sane?
When the primary is corrupt you could quickly get the size of the
device, seek to the end, read on the last 1k boundary, see if it's a
superblock, and use that as the first easily-findable backup.
Just a thought :)
-Eric
prev parent reply other threads:[~2008-09-03 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 6:57 REVIEW: Change mkfs.xfs to set primary superblock inodes in ALL secondaries Barry Naujok
2008-09-03 12:19 ` Christoph Hellwig
2008-09-03 14:11 ` Eric Sandeen [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=48BE9B2F.30606@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bnaujok@sgi.com \
--cc=xfs@oss.sgi.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