linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt McKinnon <matt@techsquare.com>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs send/receive error
Date: Wed, 13 May 2015 11:51:55 -0400	[thread overview]
Message-ID: <5553731B.9020200@techsquare.com> (raw)
In-Reply-To: <20150512144141.GG15670@merlins.org> (sfid-20150512_104155_536751_2B218AE4)

On 05/12/2015 10:41 AM, Marc MERLIN wrote:
> On Mon, May 11, 2015 at 09:00:03PM -0400, Matt McKinnon wrote:
>>> Marc
>>
>> Send box is 3.16.6 .  Receive box is 3.17.4 .
>>
>> Just upgraded the receiving box to 4.0.2 which didn't fix it, so
>> I'll schedule a reboot of the sending box.
>
> Yeah, usually these problems are because the sender sent a sequence of
> events that doesn't make sense and can't be replicated by the receiver.
> Hopefully the server upgrade will fix it.
>
> Otherwise Filipe will be very interested in getting the output of btrfs
> send -v -v from the sending and receiving side just around the time
> where it dies.
>
> Marc
>

The kernel upgrade on both ends fixed it.  Thanks Marc, Filipe.

-Matt

  reply	other threads:[~2015-05-13 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 21:38 btrfs send/receive error Matt McKinnon
2015-05-11 23:46 ` Marc MERLIN
2015-05-12  1:00   ` Matt McKinnon
2015-05-12 14:41     ` Marc MERLIN
2015-05-13 15:51       ` Matt McKinnon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-22 12:01 Lubos Kolouch
2016-06-22 16:10 ` Michael Duell
2016-06-23  7:02   ` Lubos Kolouch
2016-06-23 22:51     ` Michael Duell

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=5553731B.9020200@techsquare.com \
    --to=matt@techsquare.com \
    --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 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).