From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Alex Lyakas <alex.btrfs@zadarastorage.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Alexander Block <ablock84@googlemail.com>
Subject: Re: backref for an extent not found in send_root (!backref_ctx->found_itself)
Date: Tue, 19 Feb 2013 09:11:49 +0100 [thread overview]
Message-ID: <512333C5.2070405@jan-o-sch.net> (raw)
In-Reply-To: <CAOcd+r1wVvxwDZE7SK5iVpCMK5nMq-VD7kXo91f4+AX9LALMgw@mail.gmail.com>
Hi Alex,
On Tue, February 19, 2013 at 08:58 (+0100), Alex Lyakas wrote:
> any luck reproducing this?
Just yesterday, yes. I was busy doing non-btrfs things, I've got an idea about
the problem, but unfortunately I'm again busy doing other things right now. That
will hopefully be the last distraction before fixing this.
Thanks again for your good reproducer!
-Jan
next prev parent reply other threads:[~2013-02-19 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 16:11 backref for an extent not found in send_root (!backref_ctx->found_itself) Alex Lyakas
2013-01-29 9:07 ` Jan Schmidt
2013-01-31 19:24 ` Alex Lyakas
2013-02-19 7:58 ` Alex Lyakas
2013-02-19 8:11 ` Jan Schmidt [this message]
2013-02-21 15:35 ` [PATCH] Btrfs: fix backref walking race with tree deletions Jan Schmidt
2013-03-12 11:47 ` Alex Lyakas
2013-03-19 16:32 ` Jan Schmidt
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=512333C5.2070405@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=ablock84@googlemail.com \
--cc=alex.btrfs@zadarastorage.com \
--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).