From: Chris Mason <clm@fb.com>
To: "marc@merlins.org" <marc@merlins.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"hugo@carfax.org.uk" <hugo@carfax.org.uk>
Subject: Re: Is anyone using btrfs send/receive for backups instead of rsync?
Date: Mon, 30 Dec 2013 16:05:03 +0000 [thread overview]
Message-ID: <1388419531.11341.6.camel@ret.masoncoding.com> (raw)
In-Reply-To: <20131228182023.GG19863@merlins.org>
On Sat, 2013-12-28 at 10:20 -0800, Marc MERLIN wrote:
> On Sat, Dec 28, 2013 at 10:07:58AM -0800, Marc MERLIN wrote:
> > For instance, if I use an existing rsync destination to start syncing
> > btrfs snapshots to after that, and one file operation can't be applied
> > because let's say the destination file it's supposed to be applied to,
> > isn't there?
>
> I should have written more: I'm guessing what happens is that the btrfs
> receive fails/aborts, I get an error, I then run a manual rsync to reset
> everything to a good known state, and then continue the btrfs
> send/receive after that?
Btrfs send/receive works by matching state between snapshots on the
sending and receiving end. If you update the files manually on the
receiving end (say with rsync), it can't merge the states anymore.
-chris
next prev parent reply other threads:[~2013-12-30 16:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 17:19 Is anyone using btrfs send/receive for backups instead of rsync? Marc MERLIN
2013-12-28 17:37 ` Hugo Mills
2013-12-28 18:01 ` Emil Karlson
2013-12-28 19:34 ` Richard Michael
2013-12-28 19:52 ` Emil Karlson
2013-12-28 20:34 ` Richard Michael
2013-12-28 23:11 ` Chris Murphy
2013-12-28 23:55 ` Emil Karlson
2013-12-29 0:08 ` Chris Murphy
2013-12-29 12:39 ` Duncan
2013-12-30 0:38 ` systemd-journal, nodatacow, was: " Chris Murphy
2013-12-30 8:07 ` Duncan
2013-12-30 16:00 ` Chris Mason
2013-12-28 18:07 ` Marc MERLIN
2013-12-28 18:20 ` Marc MERLIN
2013-12-30 16:05 ` Chris Mason [this message]
2013-12-30 16:17 ` Marc MERLIN
2013-12-30 16:26 ` Chris Mason
2013-12-30 17:10 ` Marc MERLIN
2013-12-30 17:48 ` Chris Murphy
2013-12-30 17:57 ` Marc MERLIN
2013-12-30 18:39 ` Chris Murphy
2014-01-03 20:15 ` Marc MERLIN
2014-01-03 20:35 ` Chris Mason
2014-01-07 10:49 ` Is anyone using btrfs send/receive howto? Marc MERLIN
2014-01-07 10:53 ` Hugo Mills
2014-01-08 8:02 ` Marc MERLIN
2014-03-21 17:29 ` Send/Receive howto and script for others to use (was Re: Is anyone using btrfs send/receive) Marc MERLIN
2014-03-22 19:44 ` Brendan Hide
2014-03-22 19:53 ` Brendan Hide
2014-03-22 20:00 ` Marc MERLIN
2014-03-22 21:02 ` Brendan Hide
2014-03-22 21:11 ` Marc MERLIN
2014-03-23 7:12 ` Brendan Hide
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=1388419531.11341.6.camel@ret.masoncoding.com \
--to=clm@fb.com \
--cc=hugo@carfax.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.