From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] mkfs.xfs: add [-U uuid] option
Date: Mon, 21 Sep 2015 20:42:30 -0500 [thread overview]
Message-ID: <5600B206.20806@sandeen.net> (raw)
In-Reply-To: <20150921221839.GC19114@dastard>
On 9/21/15 5:18 PM, Dave Chinner wrote:
> On Mon, Sep 21, 2015 at 08:04:20PM +0300, Mika Eloranta wrote:
>> The UUID can now be optionally specified during filesystem
>> creation.
>
> Which UUID are you wanting to set - the metadata uuid or the user
> visible UUID label? Or both?
At mkfs time it should be the same / both. (the only reason they need
to diverge is a post-mkfs user-visible change on a V5 fs).
Can you explain the use case for this?
> i.e. I'm trying to work out why Why doesn't mkfs.xfs +
> xfs_admin -U <uuid> doesn't work for you?
>
> We need some explaination in the commit message so that when we look
> at this in a couple of years time we know why we added this to
> mkfs...
I'm a little curious to know why it's desired, but it's also so trivial
it seems worth accepting if it's useful to someone.
mke2fs (mkfs.ext[234]) and mkfs.btrfs can do this today as well, so
something seems to be driving the desire for the feature.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-09-22 1:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 17:04 [PATCH] mkfs.xfs: add [-U uuid] option Mika Eloranta
2015-09-21 22:18 ` Dave Chinner
2015-09-21 22:56 ` Mika Eloranta
2015-09-21 23:36 ` Dave Chinner
2015-09-22 6:43 ` Mika Eloranta
2015-09-22 7:22 ` Carlos Maiolino
2015-09-22 7:52 ` Dave Chinner
2015-09-22 8:06 ` Mika Eloranta
2015-09-22 8:25 ` Dave Chinner
2015-09-22 1:42 ` 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=5600B206.20806@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