From: Marc MERLIN <marc@merlins.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 3.15-rc5 btrfs send/receive corruption errors?
Date: Sat, 10 May 2014 17:16:50 -0700 [thread overview]
Message-ID: <20140511001649.GF27530@merlins.org> (raw)
In-Reply-To: <D55BDA6A-5DFA-4981-AC69-3156317ED169@colorremedies.com>
On Sat, May 10, 2014 at 06:06:46PM -0600, Chris Murphy wrote:
> I think the issue might be there are still problems and changing code on the receive side (btrfs-progs). The kernel side code responsible for send is probably working correctly.
Mmmh, good point, I didn't consider that.
Do you think I should downgrade btrfs-progs back down from 3.14 to 3.12?
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-05-11 0:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 22:07 3.15-rc5 btrfs send/receive corruption errors? Marc MERLIN
2014-05-10 22:42 ` Marc MERLIN
2014-05-11 0:06 ` Chris Murphy
2014-05-11 0:16 ` Marc MERLIN [this message]
2014-05-11 0:50 ` Chris Murphy
[not found] ` <E1WiphR-0003MN-50@legolas.merlins.org>
2014-05-11 2:29 ` 3.15-rc5 btrfs send/receive corruption errors? Does scrub warn of silent corruption? Marc MERLIN
2014-05-12 23:26 ` Marc MERLIN
2014-05-13 20:11 ` Filipe David Manana
2014-05-14 13:26 ` Marc MERLIN
2014-05-17 22:23 ` Marc MERLIN
2014-05-19 12:54 ` Filipe David Manana
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=20140511001649.GF27530@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).