From: David Goodwin <david@codepoets.co.uk>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Mount multiple file system with the same UUID
Date: Fri, 17 Apr 2015 10:56:55 +0100 [thread overview]
Message-ID: <5530D8E7.90301@codepoets.co.uk> (raw)
In-Reply-To: <SNT150-W75F9A63B7062DE5A608491A1E30@phx.gbl>
On 17/04/15 10:20, WangMike wrote:
> Dear all,
>
> We know that one cannot mount multiple btrfs file systems which contain the same UUID (for example, snapshot ).
>
> Is it possible to make use of "mount namespace" achieve that? means, if the btrfs file system in different namespace can contain the same UUID.
>
I've encountered this problem using EC2 EBS volumes.
(the 'ghost image' (AMI) contains btrfs filesystems. This results in all
child VMs having EBS volumes sharing the same UUID ... and it's then not
being possible to move volumes around.)
I'm interested to know if there's a possible solution, aside hoping you
can run mkfs.btrfs on first boot...
David.
next prev parent reply other threads:[~2015-04-17 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 9:20 Mount multiple file system with the same UUID WangMike
2015-04-17 9:56 ` David Goodwin [this message]
2015-04-17 15:04 ` Chris Murphy
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=5530D8E7.90301@codepoets.co.uk \
--to=david@codepoets.co.uk \
--cc=linux-btrfs@vger.kernel.org \
/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