From: Filipe David Manana <fdmanana@gmail.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: David Sterba <dsterba@suse.cz>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
clm@fb.com, jbacik@fb.com
Subject: Re: [PATCH] Btrfs: optimize btrfs_lookup_extent_info() - extent refcount mismatches?
Date: Sun, 8 Dec 2013 00:32:08 +0000 [thread overview]
Message-ID: <CAL3q7H4RGpAc1_Gedq6GeqK3HDZ3=asLHUk8Vn=_JYd56K6ufw@mail.gmail.com> (raw)
In-Reply-To: <CAEzrpqfGNbFQ8wG7SWVJOp3pM3BwfAdO79VrOK-t9JiUFNCkUQ@mail.gmail.com>
On Tue, Dec 3, 2013 at 6:28 PM, Josef Bacik <josef@toxicpanda.com> wrote:
> On Tue, Dec 3, 2013 at 8:43 AM, David Sterba <dsterba@suse.cz> wrote:
>> On Fri, Nov 29, 2013 at 07:55:37PM +0000, Filipe David Manana wrote:
>>> On Fri, Nov 29, 2013 at 3:45 PM, David Sterba <dsterba@suse.cz> wrote:
>>> > Hi,
>>> >
>>> > On Fri, Jul 05, 2013 at 09:32:05PM +0100, Filipe David Borba Manana wrote:
>>> >> If we're looking for a metadata item in the tree and the
>>> >> search fails with return value of 1, and the slot doesn't
>>> >> point to the first item in the leaf, check if the previous
>>> >> item in the leaf corresponds to an extent item for the same
>>> >> object id - if it does, then don't do another tree search
>>> >> to get it.
>>> >
>>> > I'm suspecting this patch to cause some trouble, see
>>> > https://bugzilla.kernel.org/show_bug.cgi?id=64961
>>>
>>> What makes you believe the problem is exactly in this function?
>>
>> It was a first guess based on the stacktraces and last patch that
>> touched the code. I've replied to mailinlist because it has higher
>> visibility, number of bugreports in balance/relocation has been
>> increasing lately (not blaming you).
>>
>>> I read it again, and I can't see how it can miss an extent item that
>>> it couldn't before, specially without skinny metadata enabled. Did
>>> the fs had skinny metadata enabled?
>>
>> According to the updated bugzilla yes, and that's another possible
>> cause although we haven't seen bugs with skinny metadata yet. There's
>> another bugreport that has them enabled,
>> https://bugzilla.kernel.org/show_bug.cgi?id=66411
I found an issue in btrfs_lookup_extent_info() when skinny metadata is
enabled. It can actually miss existing skinny extent items.
The following patch fixes it and explains in detail the issue:
https://patchwork.kernel.org/patch/3305521/
thanks
>>
>
> I've been seeing similar issues while testing my qgroups patches that
> I don't think is related to my qgroup work. I'm going to try and
> track it down this week but I may not get to it until next week.
> Thanks,
>
> Josef
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
prev parent reply other threads:[~2013-12-08 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 15:45 [PATCH] Btrfs: optimize btrfs_lookup_extent_info() - extent refcount mismatches? David Sterba
2013-11-29 19:55 ` Filipe David Manana
2013-12-03 16:43 ` David Sterba
2013-12-03 18:28 ` Josef Bacik
2013-12-08 0:32 ` Filipe David Manana [this message]
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='CAL3q7H4RGpAc1_Gedq6GeqK3HDZ3=asLHUk8Vn=_JYd56K6ufw@mail.gmail.com' \
--to=fdmanana@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=josef@toxicpanda.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).