From: Lubos Kolouch <kolcon@kolcon.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs send/receive error
Date: Thu, 23 Jun 2016 07:02:18 +0000 (UTC) [thread overview]
Message-ID: <loom.20160623T090018-726@post.gmane.org> (raw)
In-Reply-To: b3bf0ff9-175b-29fa-485d-4818811619eb@rub.de
Michael Duell <michael.duell <at> rub.de> writes:
>
> Hallo Lubos!
>
> I have got the same problems with send/receive. Had those problems
> for several weeks or months now. Not sure when those started.
>
> These send/receive problems are known and there are several bug
> reports all over the internet and also on this list.
>
> Not sure if or when this gets fixed. It's broken atm.
>
> Michael
>
Hallo Michael,
I would like to help to debug the issue. Something I can do/get
logs/whatever to speed up the root cause analysis and get it fixed?
MfG/Best regards,
Lubos
next prev parent reply other threads:[~2016-06-23 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 12:01 btrfs send/receive error Lubos Kolouch
2016-06-22 16:10 ` Michael Duell
2016-06-23 7:02 ` Lubos Kolouch [this message]
2016-06-23 22:51 ` Michael Duell
-- strict thread matches above, loose matches on Subject: below --
2015-05-11 21:38 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
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=loom.20160623T090018-726@post.gmane.org \
--to=kolcon@kolcon.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;
as well as URLs for NNTP newsgroup(s).