Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Jim Salter <jim@jrs-s.net>
To: Ames Cornish <gmane@pub.cornishes.net>, linux-btrfs@vger.kernel.org
Subject: Re: Announcement: buttersink - like rsync for btrfs snapshots
Date: Mon, 11 Aug 2014 13:57:29 -0400	[thread overview]
Message-ID: <53E90409.5050105@jrs-s.net> (raw)
In-Reply-To: <loom.20140811T193907-62@post.gmane.org>

How has it been for reliability?

I wrote a btrsync app a while back, and the app /itself/ worked fine, 
but the btrfs send / btrfs receive itself proved problematic.  Since 
btrfs would keep a partial receive - with no easy way to tell whether a 
receive WAS partial or full - I would inevitably end up with interrupted 
sends causing a problem that couldn't be resolved without manually 
deleting snapshots on the target end haphazardly until I nailed the 
incomplete one.

On 08/11/2014 01:49 PM, Ames Cornish wrote:
> I've written a utility to help me with using btrfs send and receive for
> backups or other synchronization, and I'd love to get feedback on it.
>
> As of this release, buttersink will synchronize a set of read-only snapshots
> in a btrfs filesystem to an Amazon S3 bucket, and vice-versa.  It
> intelligently picks parent snapshots to "diff" from, so that a minimal amount
> of data needs to be sent over the wire and stored in the backend.
>
> The utility is on PyPi as "buttersink", and the GitHub page is here:
>    https://github.com/AmesCornish/buttersink.
>
> Thanks in advance for any feedback!
>
> - Ames
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2014-08-11 18:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 17:49 Announcement: buttersink - like rsync for btrfs snapshots Ames Cornish
2014-08-11 17:57 ` Jim Salter [this message]
     [not found]   ` <CAP6pX24fWPrZ3368WxaViYT2_N2WcCWtso3KqxF_SRrDTS54xQ@mail.gmail.com>
     [not found]     ` <CAP6pX26e79LZzMMwdeE7JOeGyoLtRxqvJhScBX1LDEwJ7UNe3Q@mail.gmail.com>
2014-08-11 18:08       ` Jim Salter
2014-08-12 17:44         ` Clemens Eisserer
2014-08-11 18:08   ` Ames Cornish
  -- strict thread matches above, loose matches on Subject: below --
2014-08-24  3:08 Shriramana Sharma

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=53E90409.5050105@jrs-s.net \
    --to=jim@jrs-s.net \
    --cc=gmane@pub.cornishes.net \
    --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