public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Mika Eloranta <mika.eloranta@ohmu.fi>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] mkfs.xfs: add [-U uuid] option
Date: Tue, 22 Sep 2015 09:36:27 +1000	[thread overview]
Message-ID: <20150921233627.GE19114@dastard> (raw)
In-Reply-To: <2640913C-6C95-4128-9055-B155AECA0206@ohmu.fi>

On Tue, Sep 22, 2015 at 01:56:53AM +0300, Mika Eloranta wrote:
> On 22 Sep 2015, at 01:18, Dave Chinner <david@fromorbit.com>
> 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? 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?
> 
> I want to set the user visible UUID (same as xfs_admin -U/-u).
> Whether this impacts the "metadata uuid” or not, I do not
> know, I’m not an expert on the XFS internals, just a user.

Which tells me what I need to know - You are trying to use the UUID
as a user controlled filesystem label. Funnily enough, we have a
thing for this already - a user controlled filesystem label:

# mkfs.xfs -L "label" ....

It's 12 characters long, so more than enough for any sort of unique
identification scheme you want to use for your filesystems.
xfs_admin enables you to change it after the fact, all major
filesystems support it and all the infrastructure know about it
(lsblk, /etc/fstab. /dev/disk/by-label, etc) so using it is no
different to using UUIDs. Except that, unlike UUIDs, you can make
fileystem labels human readable. :)

Perhaps you should try using filesystem labels seeing as everything
you need is already there?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-09-21 23:36 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 [this message]
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

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=20150921233627.GE19114@dastard \
    --to=david@fromorbit.com \
    --cc=mika.eloranta@ohmu.fi \
    --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