From: Gabriel <g2p.code@gmail.com>
To: "Kevin O'Kelley" <kevin@kevinokelley.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Hugo Mills <hugo@carfax.org.uk>
Subject: Re: Two identical copies of an image mounted result in changes to both images if only one is modified
Date: Thu, 20 Jun 2013 15:29:43 +0200 [thread overview]
Message-ID: <51C303C7.4020102@gmail.com> (raw)
In-Reply-To: <FDFB4977-0209-4F58-92CB-EF80E3575873@kevinokelley.com>
> Thank you for your reply. I appreciate it. Unfortunately this issue is a deal killer for us. The ability to take very fast snapshots and replicate them to another site is key for us. We just can't us Btrfs with this setup. That's too bad. Good luck and thank you.
The issue we were discussing is: how to fail early when there are
duplicate UUIDs.
Duplicate UUIDs will never be supported.
If *your* problem has to do with fast snapshots and fast replication,
that's supported, see btrfs send/receive.
next prev parent reply other threads:[~2013-06-20 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 8:47 Two identical copies of an image mounted result in changes to both images if only one is modified Clemens Eisserer
2013-06-20 9:11 ` Fajar A. Nugraha
2013-06-20 9:16 ` Hugo Mills
2013-06-20 10:22 ` Gabriel de Perthuis
2013-06-20 10:34 ` Hugo Mills
2013-06-20 10:41 ` Gabriel de Perthuis
2013-06-20 10:56 ` Hugo Mills
2013-06-20 13:22 ` Kevin O'Kelley
2013-06-20 13:28 ` Hugo Mills
2013-06-20 13:29 ` Gabriel [this message]
2013-06-20 13:32 ` Hugo Mills
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=51C303C7.4020102@gmail.com \
--to=g2p.code@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=kevin@kevinokelley.com \
--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).