From: Dave Chinner <david@fromorbit.com>
To: "Carlos E. R." <carlos.e.r@opensuse.org>
Cc: XFS mailing list <xfs@oss.sgi.com>
Subject: Re: Proposal/RFC: new metadata-specific UUID for V5 supers
Date: Tue, 28 Apr 2015 11:42:24 +1000 [thread overview]
Message-ID: <20150428014224.GT15810@dastard> (raw)
In-Reply-To: <553EE3FA.9050603@opensuse.org>
On Tue, Apr 28, 2015 at 03:35:54AM +0200, Carlos E. R. wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 2015-04-28 03:20, Dave Chinner wrote:
>
> >> Well, it's just the loss of ability to change UUID, which is
> >> something People Used To Do(tm), and now can't. It does come up.
> >> Honestly if it had been done from day 0, it'd be a no-brainer I
> >> think. Doing it now, with an incompat flag, might not be a
> >> reasonable tradeoff.
> >
> > 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...
>
> As a plain user, I can say that I have needed to mount both the
> filesystem and its backup image, but Linux refused on the basis of the
> id being the same. Of course, all identifiers are the same, label and
> uuid.
Yes, that's the XFS UUID mount checking refusing to mount without the
"nouuid" mount option because of the duplicate UUID. XFS doesn't care
about whether there are duplicate labels or not, so removing the
UUID checking would solve your problem.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-04-28 1:48 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 [this message]
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=20150428014224.GT15810@dastard \
--to=david@fromorbit.com \
--cc=carlos.e.r@opensuse.org \
--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