From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Proposal/RFC: new metadata-specific UUID for V5 supers
Date: Mon, 27 Apr 2015 17:10:25 -0500 [thread overview]
Message-ID: <553EB3D1.10602@sandeen.net> (raw)
Wanted to float this & see what people think...
Today, it's impossible (FSVO impossible) to change a V5 filesystem's
UUID, because that UUID is stamped into every bit of metadata. If
not impossible, it's unimplemented and any implementation would be
terribly inefficient.
With 20/20 hindsight, an sb_meta_uuid field, separate from the sb_uuid
field that is userspace-visible, would have avoided this problem.
We can certainly add it, but it'd need to be an incompat change, because
old kernels would see this as catastrophic mismatching of every bit
of metadata on a V5 superblock filesystem.
Other than that little problem (o_O) it'd be trivial to implement.
Thoughts?
Thanks,
-Eric
p.s. Thanks to Zach for making me think about this, but I'm not
blaming him for my decision to propose it. ;)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-04-27 22:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 22:10 Eric Sandeen [this message]
2015-04-27 23:37 ` Proposal/RFC: new metadata-specific UUID for V5 supers Dave Chinner
2015-04-28 0:52 ` Eric Sandeen
2015-04-28 1:20 ` Dave Chinner
2015-04-28 1:35 ` Carlos E. R.
2015-04-28 1:42 ` Dave Chinner
2015-04-28 2:06 ` Eric Sandeen
2015-04-29 18:38 ` Eric Sandeen
2015-04-29 21:27 ` Dave Chinner
2015-04-30 4:50 ` [PATCH RFC 1/2] xfs: add sb_meta_uuid field to superblock Eric Sandeen
2015-04-30 5:07 ` Eric Sandeen
2015-04-30 4:55 ` [PATCH RFC 2/2] xfsprogs: add support for sb_meta_uuid 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=553EB3D1.10602@sandeen.net \
--to=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