From: Adam Borowski <kilobyte@angband.pl>
To: linux-btrfs@vger.kernel.org
Subject: Re: does btrfs-receive use/compare the checksums from the btrfs-send side?
Date: Sun, 28 Aug 2016 22:19:08 +0200 [thread overview]
Message-ID: <20160828201908.GA19993@angband.pl> (raw)
In-Reply-To: <1472406642.7253.1.camel@scientia.net>
On Sun, Aug 28, 2016 at 07:50:42PM +0200, Christoph Anton Mitterer wrote:
> On Sun, 2016-08-28 at 11:35 -0600, Chris Murphy wrote:
> > I don't see evidence of them in the btrfs send file, so I don't think
> > csums are in the stream.
>
> hmm... isn't that kinda unfortunate not to make use of the information
> that's already there?
Transports over which you're likely to send a filesystem stream already
protect against corruption.
It'd still be nice to have something for those which don't, of course.
--
An imaginary friend squared is a real enemy.
next prev parent reply other threads:[~2016-08-28 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 3:46 does btrfs-receive use/compare the checksums from the btrfs-send side? Christoph Anton Mitterer
2016-08-28 17:35 ` Chris Murphy
2016-08-28 17:50 ` Christoph Anton Mitterer
2016-08-28 20:19 ` Adam Borowski [this message]
2016-08-28 20:25 ` Christoph Anton Mitterer
2016-08-30 17:14 ` Sean Greenslade
2016-08-29 8:25 ` Qu Wenruo
2016-09-04 4:29 ` Christoph Anton Mitterer
2016-09-05 7:45 ` Qu Wenruo
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=20160828201908.GA19993@angband.pl \
--to=kilobyte@angband.pl \
--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 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.