From: Eric Sandeen <sandeen@sandeen.net>
To: markgw@sgi.com
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: Tue, 25 Mar 2008 21:07:18 -0500 [thread overview]
Message-ID: <47E9AFD6.3050304@sandeen.net> (raw)
In-Reply-To: <47E9AC67.8070809@sgi.com>
Mark Goodwin wrote:
>
> Eric Sandeen wrote:
>> 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 ...
If not found at the end, just go back to the original search scheme, I'd
say...
-Eric
prev parent reply other threads:[~2008-03-26 2:06 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
2008-03-26 2:07 ` 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=47E9AFD6.3050304@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bnaujok@sgi.com \
--cc=markgw@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 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.