From: Jim Salter <jim@jrs-s.net>
To: Ames Cornish <ames@montebellopartners.com>
Cc: 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 14:08:11 -0400 [thread overview]
Message-ID: <53E9068B.3090005@jrs-s.net> (raw)
In-Reply-To: <CAP6pX26e79LZzMMwdeE7JOeGyoLtRxqvJhScBX1LDEwJ7UNe3Q@mail.gmail.com>
To any core btrfs devs who are listening and care - the unreliability of
btrfs send/receive is IMO the single biggest roadblock to adoption of
btrfs as a serious next-gen FS.
I can live with occasional corner-case performance issues, I can even
live with (very) occasional filesystem corruption... IF I can rely on
replication to keep my data safe on another box. Without the
replication, there's just no reasonable case to be made to replace ZFS.
On 08/11/2014 02:05 PM, Ames Cornish wrote:
> Jim,
>
> btrfs send reliability has been an issue, though I've been able to
> successfully use it for my backups. buttersink usually detects the
> errors and will either move the destination snapshot to mark it as
> partial/failed (for btrfs), or cancel and delete the partial upload
> (for S3). I've also found that it helps to wait a while (e.g. 30
> seconds) after any volume deletes before trying the send/sync. I hope
> btrfs-progs will get more reliable, too.
>
> - Ames
next prev parent reply other threads:[~2014-08-11 18:08 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
[not found] ` <CAP6pX24fWPrZ3368WxaViYT2_N2WcCWtso3KqxF_SRrDTS54xQ@mail.gmail.com>
[not found] ` <CAP6pX26e79LZzMMwdeE7JOeGyoLtRxqvJhScBX1LDEwJ7UNe3Q@mail.gmail.com>
2014-08-11 18:08 ` Jim Salter [this message]
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=53E9068B.3090005@jrs-s.net \
--to=jim@jrs-s.net \
--cc=ames@montebellopartners.com \
--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