From: Hugo Mills <hugo@carfax.org.uk>
To: Vincent Olivier <vincent@up4.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Send/Receive Use Case
Date: Sat, 27 Jun 2015 14:21:32 +0000 [thread overview]
Message-ID: <20150627142132.GI16065@carfax.org.uk> (raw)
In-Reply-To: <F2771637-3D78-4332-AB96-993069114030@up4.com>
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
On Sat, Jun 27, 2015 at 10:04:28AM -0400, Vincent Olivier wrote:
> Hi,
>
> 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 ? And to subsequently mix rsync and send-receive ? Provided that snapshots are made accordingly.
Probably. It depends on exctly how you want to use them.
> 2) Is possible to “send" a snapshot diff to disk and then “receive" it from the said disk into a remote filesystem ? I have two very large and physically distant btrfs filesystems. It would be more economical to juste dump snapshot diffs to disk for transport instead of the network.
Yes, that's perfectly possible.
> 3) How are “conflicts” handled by send-receive if at all ?
There are no conflicts possible, due to the requirement of all the
subvolumes involved in the send/receive process being read-only.
(Actually, that's not quite true -- you can make a subvolume
read/write, and then read-only again. In that case, the receive will
probably fail, leaving the received subvolume in a partially-created
state).
> 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 ?
It'll be ignored. The FS doesn't keep track of how it reached a
particular state -- only what that state is.
Hugo.
--
Hugo Mills | IMPROVE YOUR ORGANISMS!!
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Subject line of spam email
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-06-27 14:21 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
2015-06-27 14:21 ` Hugo Mills [this message]
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=20150627142132.GI16065@carfax.org.uk \
--to=hugo@carfax.org.uk \
--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