public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.de>
To: fdmanana@gmail.com, Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Nikolay Borisov <nborisov@suse.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: ctree: Dump the leaf before BUG_ON()
Date: Wed, 24 Apr 2019 21:55:59 +0800	[thread overview]
Message-ID: <82265550-eccb-6429-62e8-9623f9ffb3ad@suse.de> (raw)
In-Reply-To: <CAL3q7H5ZZU0eEwUMH_SLcCuHd2jD-dEOFeWQBquNWFZyLoLV2A@mail.gmail.com>



On 2019/4/24 下午9:53, Filipe Manana wrote:
> On Wed, Apr 24, 2019 at 1:57 PM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>>
>>
>> On 2019/4/24 下午8:52, Nikolay Borisov wrote:
>>>
>>>
>>> On 24.04.19 г. 15:48 ч., Qu Wenruo wrote:
>>>> Let's dump the leaf content before triggering BUG_ON() so that we can
>>>> have some clue on what's going wrong.
>>>> The output of tree locks should help us to debug such problem.
>>>>
>>>
>>> The reason is some sort of in-memory corruption/confusion of the extent
>>> maps, causing overlapping extents. However so far it hasn't been
>>> possible to reproduce that on-demand to actually debug it. Filipe
>>> suspected it has to do with extent mapping merging logic. This only
>>> occurs when working with the log tree which takes its data from the
>>> in-memory extent mapping tree.
>>
>> Anyway, this won't hurt. right?
>>
>> If it gives us some clue, that's the best case.
>> If not, it won't make the current situation worse, right?
> 
> Right, but dumping the leaf alone, may not tell you much (I've been there).
> Printing the new key and slot, together with the leaf dump, helps much more.

Right, I'd add them.

Thanks,
Qu

> 
> Thanks.
> 
>>
>> Thanks,
>> Qu
> 
> 
> 

      reply	other threads:[~2019-04-24 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 12:48 [PATCH] btrfs: ctree: Dump the leaf before BUG_ON() Qu Wenruo
2019-04-24 12:52 ` Nikolay Borisov
2019-04-24 12:55   ` Qu Wenruo
2019-04-24 13:53     ` Filipe Manana
2019-04-24 13:55       ` Qu Wenruo [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=82265550-eccb-6429-62e8-9623f9ffb3ad@suse.de \
    --to=wqu@suse.de \
    --cc=fdmanana@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=quwenruo.btrfs@gmx.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