From: Mark Goodwin <markgw@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Barry Naujok <bnaujok@sgi.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: REVIEW: Write primary superblock info to ALL secondaries during mkfs
Date: Wed, 26 Mar 2008 12:52:39 +1100 [thread overview]
Message-ID: <47E9AC67.8070809@sgi.com> (raw)
In-Reply-To: <47E8F5BD.7000601@sandeen.net>
Eric Sandeen wrote:
> Barry Naujok wrote:
>> Secondaries should contain redundant information from the primary
>> superblock. It does this for the filesystem geometry information,
>> but not inode values (rootino, rt inos, quota inos).
>>
>> This patch updates all the secondaries from the primary just before
>> it marks the filesystem as good to go.
>>
>> Unfortunately, this also affects the output of xfs_repair during
>> QA 030 and 178 which restores the primary superblock from the
>> secondaries.
>>
>> Now that the secondaries have valid inode values, xfs_repair
>> does not have to restore them to the correct values after copying
>> the secondary into the primary.
>>
>> Attached is the mkfs.xfs patch and also the updated golden
>> outputs for QA 030 and 178.
>>
>> The next step after this is to enhance xfs_repair to be more
>> thorough in checking the secondaries during Phase 1.
>
> One related thing I'd always wondered about was stamping a secondary at
> the very end of the device (and therefore shrinking the fs by just a
> bit) - repair could then do a quick check at the end of the device
> before resorting to scanning for the 2nd backup... would this make any
> sense?
I guess it might, Barry what do you think? Probably makes grow a bit
more complicated. What would repair do if it doesn't find the backup
SB at the end of the device? We'd need a new SB flag to indicate it's
supposed to be there, which seems a bit chicken-and-egg'ish ...
Cheers
>
> -Eric
>
>
--
Mark Goodwin markgw@sgi.com
Engineering Manager for XFS and PCP Phone: +61-3-99631937
SGI Australian Software Group Cell: +61-4-18969583
-------------------------------------------------------------
next prev parent reply other threads:[~2008-03-26 1:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 5:39 REVIEW: Write primary superblock info to ALL secondaries during mkfs Barry Naujok
2008-03-25 6:00 ` David Chinner
2008-03-25 6:16 ` Barry Naujok
2008-03-25 12:53 ` Eric Sandeen
2008-03-26 1:52 ` Mark Goodwin [this message]
2008-03-26 2:07 ` Eric Sandeen
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=47E9AC67.8070809@sgi.com \
--to=markgw@sgi.com \
--cc=bnaujok@sgi.com \
--cc=sandeen@sandeen.net \
--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