From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Proposal/RFC: new metadata-specific UUID for V5 supers
Date: Wed, 29 Apr 2015 13:38:53 -0500 [thread overview]
Message-ID: <5541253D.4090701@sandeen.net> (raw)
In-Reply-To: <553EEB36.4080200@sandeen.net>
On 4/27/15 9:06 PM, Eric Sandeen wrote:
> On 4/27/15 8:20 PM, Dave Chinner wrote:
>
>> I think that labels are a far better way of dealing with this
>> problem. Get rid of the UUID mount checking (and hence the nouuid
>> mount option), and tell people to use by-label instead of by-uuid to
>> identify their filesystems when doing clones and snapshots. Labels
>> make it much easier for humans to identify the filesystem than
>> UUIDs...
>
> I suppose so. Withdrawn. ;)
One more thought. ;)
It'd be quite possible to keep defaults compatible with old kernels,
and only set the new feature if/when a user requests a UUID change.
If UUID changes are rare, it'll rarely matter; if they are required,
it'll be possible. I might send a patch just to make the discussion
a bit more concrete.
Thanks,
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-04-29 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 22:10 Proposal/RFC: new metadata-specific UUID for V5 supers Eric Sandeen
2015-04-27 23:37 ` 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 [this message]
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=5541253D.4090701@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.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