From: Nikolay Borisov <kernel@kyup.com>
To: Chris Mason <clm@fb.com>, linux-btrfs@vger.kernel.org
Cc: SiteGround Operations <operations@siteground.com>
Subject: Re: Crash in btrfs_uuid_tree_iterate during mount
Date: Mon, 29 Aug 2016 10:25:03 +0300 [thread overview]
Message-ID: <57C3E34F.30804@kyup.com> (raw)
In-Reply-To: <b369cabe-9269-800c-cce7-5f5c71147660@fb.com>
On 08/08/2016 05:24 PM, Chris Mason wrote:
> On 08/08/2016 10:21 AM, Nikolay Borisov wrote:
>>
>>
>> On 08/08/2016 05:16 PM, Chris Mason wrote:
>>>
>>> Fantastic, thanks again for digging through it. Making the patch is
>>> much easier than testing the patch in this case. If you can trigger
>>> this semi-reliably, we can add some debugging to make sure we're not
>>> papering over some other problem.
>>
>> I don;'t have a reproducer per-se, but I have a fair number of servers,
>> whose workload causes the issue, so if I patch btrfs and apply it to
>> 5-10 server I;d expect at least one of them to show what the real
>> issue is.
>>
>
> Ok, I'll try and get a patch out before my vacation on Wednesday. Thanks!
Ping
>
> -chris
next prev parent reply other threads:[~2016-08-29 7:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 11:08 Crash in btrfs_uuid_tree_iterate during mount Nikolay Borisov
2016-08-05 15:12 ` Chris Mason
2016-08-05 19:14 ` Nikolay Borisov
2016-08-08 10:49 ` Nikolay Borisov
2016-08-08 14:16 ` Chris Mason
2016-08-08 14:21 ` Nikolay Borisov
2016-08-08 14:24 ` Chris Mason
2016-08-29 7:25 ` Nikolay Borisov [this message]
2016-09-07 7:38 ` [PATCH] btrfs: Fix handling of -ENOENT from btrfs_uuid_iter_rem Nikolay Borisov
2016-09-19 18:13 ` David Sterba
2016-09-19 18:49 ` Chris Mason
2016-09-19 20:18 ` David Sterba
[not found] ` <CAJFSNy5eOdkn=YSA1-T7goOUNuX6ozUiGAM3tCTq7dvzsiJCug@mail.gmail.com>
2016-09-20 7:36 ` Nikolay Borisov
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=57C3E34F.30804@kyup.com \
--to=kernel@kyup.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=operations@siteground.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.