From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: An issue when mounting the dd-copied partition and the original one together
Date: Fri, 20 Apr 2012 17:20:42 +1000 [thread overview]
Message-ID: <201204201720.44788.chris@csamuel.org> (raw)
In-Reply-To: <CAOLNCyrvxNi-wKYdPaUX9Qvpzi7RhVjDgmig-Mr1_M5HmXza2Q@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1257 bytes --]
On Friday 20 April 2012 16:49:48 Tydus Ken wrote:
> I guess there's something wrong with btrfs in how to deal with two
> partition with same UUID or something else, but I'm not sure.
I don't believe that btrfs can cope with partitions with the same UID.
A pointer here from Auke in July 2011:
http://marc.info/?l=linux-btrfs&m=131161949201880&w=2
# Resetting the UUID on btrfs isn't a quick-and-easy thing - you
# have to walk the entire tree and change every object. We've got
# a bad-hack in meego that uses btrfs-debug-tree and changes the
# UUID while it runs the entire tree, but it's ugly as hell.
#
# You shouldn't clone btrfs really, just make a new filesystem.
That hack is for an unmounted filesystem, but I don't believe it's
been shared on this list.
Jan Schmidt was working on a "btrfs send" type command to help with
this, but I've not heard anything recently (last December he posted
that he was distracted by the backref-walking code which was a
necessary precursor for the send/receive code).
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2012-04-20 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 6:49 An issue when mounting the dd-copied partition and the original one together Tydus Ken
2012-04-20 7:20 ` Chris Samuel [this message]
2012-04-20 7:40 ` Jan Schmidt
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=201204201720.44788.chris@csamuel.org \
--to=chris@csamuel.org \
--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;
as well as URLs for NNTP newsgroup(s).