From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Vincent Olivier <vincent@up4.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Send/Receive Use Case
Date: Sat, 27 Jun 2015 16:18:11 +0200 [thread overview]
Message-ID: <2261769.FUJI4BnnUt@zafu> (raw)
In-Reply-To: <F2771637-3D78-4332-AB96-993069114030@up4.com>
Hi,
Le samedi 27 juin 2015 10:04:28 Vincent Olivier a écrit :
>
> There are 4 things I’m not sure about re:send/receive.
>
> 1) Is it possible to first copy things on a file system using rsync and then
> use send-receive ?
NO. You need to start with a BTRFS snapshot send/receive to be able to
continue with differential send/receives.
> And to subsequently mix rsync and send-receive ?
NOPE.
> 2) Is possible to “send" a snapshot diff to disk and then “receive" it from
> the said disk into a remote filesystem ?
YES.
> 3) How are “conflicts” handled by send-receive if at all ?
No way. Incremental send/receive are possible only if you have the exact
(binary) (read-only) "parent" snapshot on both filesystems. There cannot be
"conflicts" and incremental send/receive is not possible in any other
situation.
> 4) If a file is created, modified and then deleted in-between two snapshots
> is it ignored by send/receive or does send/receive "re-enacts” the journal
> exactly ?
If anything is created/modified/deleted, the medatata being COW, will differ.
Incremental send/receive, being the "binary diff" between filesystem states,
will reflect this difference.
Kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
next prev parent reply other threads:[~2015-06-27 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 14:04 Send/Receive Use Case Vincent Olivier
2015-06-27 14:18 ` Swâmi Petaramesh [this message]
2015-06-27 14:21 ` Hugo Mills
2015-06-27 14:34 ` Vincent Olivier
2015-07-10 19:03 ` Vincent Olivier
2015-07-10 19:11 ` Hugo Mills
2015-07-10 19:12 ` Vincent Olivier
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=2261769.FUJI4BnnUt@zafu \
--to=swami@petaramesh.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=vincent@up4.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