From: Chris Samuel <chris@csamuel.org>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Recovering a file from a snapshot without duplicating its blocks (--reflink across devs?)
Date: Tue, 05 Jun 2012 13:42:50 +1000 [thread overview]
Message-ID: <4FCD803A.2070906@csamuel.org> (raw)
In-Reply-To: <20120605030100.GA7572@merlins.org>
On 05/06/12 13:01, Marc MERLIN wrote:
> First I though, I sure would be nice if I could take btrfs to reference
> the same blocks from the snapshot to my current image.
> But, --reflink failed across devices nodes, so I was forced to
> copy/duplicate the blocks (36GB).
Patches for this were posted over a year ago, but it was NAK'd by
Christoph Hellwig. I don't know if it's got any further since then. :-(
Patch description:
http://www.spinics.net/lists/linux-btrfs/msg09226.html
NAK:
http://www.spinics.net/lists/linux-btrfs/msg09229.html
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
next prev parent reply other threads:[~2012-06-05 3:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 3:01 Recovering a file from a snapshot without duplicating its blocks (--reflink across devs?) Marc MERLIN
2012-06-05 3:42 ` Chris Samuel [this message]
2012-06-05 11:54 ` Marc MERLIN
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=4FCD803A.2070906@csamuel.org \
--to=chris@csamuel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).