From: Josef Bacik <jbacik@fb.com>
To: Abbas <mickylmartin@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: Sending incremental backup causes deadlock (3.14.3)
Date: Fri, 9 May 2014 13:22:27 -0400 [thread overview]
Message-ID: <536D0ED3.2050602@fb.com> (raw)
In-Reply-To: <CAKAA-n=_jMyWFbfcGvMsMDJg3t7VpRegDDDybEeQ5oxof8graA@mail.gmail.com>
On 05/09/2014 11:41 AM, Abbas wrote:
> Has anyone else experienced a deadlock while doing an incremental send
> / receive?
>
> # uname -r
> 3.14.3-1.el6.elrepo.x86_64
>
> # btrfs version
> Btrfs v3.14.1
>
> Initial send works well but sending incremental snapshots just HALTS:
>
> # btrfs send -vvvv -p test/snap-2014-05-09-13:29:04
> test/snap-2014-05-09-13:32:58 | btrfs receive -vvvv backup/test
> At subvol test/snap-2014-05-09-13:32:58
> At snapshot snap-2014-05-09-13:32:58
> receiving snapshot snap-2014-05-09-13:32:58
> uuid=8cde86f7-6ded-5046-a55c-3a0d40e7a2fc, ctransid=0
> parent_uuid=1a2a9dc2-c271-524f-bd01-b671da630446, parent_ctransid=0
> ...
>
Known problem, fixed in 3.15-rc1. Thanks,
Josef
next prev parent reply other threads:[~2014-05-09 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 15:41 Sending incremental backup causes deadlock (3.14.3) Abbas
2014-05-09 17:22 ` Josef Bacik [this message]
2014-05-10 8:04 ` Chris Samuel
2014-05-12 15:22 ` Josef Bacik
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=536D0ED3.2050602@fb.com \
--to=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mickylmartin@gmail.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).