From: Chris Mason <clm@fb.com>
To: Gabriel C <nix.or.die@gmail.com>, <linux-btrfs@vger.kernel.org>
Cc: <quwenruo@cn.fujitsu.com>
Subject: Re: A lot warnings in dmesg while running thunderbird
Date: Fri, 15 Jul 2016 17:08:37 -0400 [thread overview]
Message-ID: <a17a5af4-cf5e-cb4e-de09-4aeb8282e891@fb.com> (raw)
In-Reply-To: <50805ba8-2681-8606-79b3-add5b47b864f@fb.com>
On 07/15/2016 03:35 PM, Chris Mason wrote:
>
>
> On 07/07/2016 06:24 AM, Gabriel C wrote:
>> Hi,
>>
>> while running thunderbird on linux 4.6.3 and 4.7.0-rc6 ( didn't tested
>> other versions )
>> I trigger the following :
>>
>>
>> [ 6393.305675] WARNING: CPU: 6 PID: 5870 at fs/btrfs/inode.c:9306
>> btrfs_destroy_inode+0x22e/0x2a0 [btrfs]
>
> Every time I've reproduced this, I've hit a warning in extent-tree.c
> about trying to decrement bytes_may_use too far. Then I get enospc
> on every operation.
>
> Josef fixed a few corner cases here with his new enospc changes, and I'm
> not able to trigger (yet) with those applied. Dave Sterba has them all
> in his for-next branch:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
>
> Can you please try that on top of v4.7-rc7
A few hours later and it reproduced on this kernel too. What must be
happening is we're freeing too many bytes from bytes_may_use.
I'll get tracing in and nail it down.
-chris
prev parent reply other threads:[~2016-07-15 21:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 10:24 A lot warnings in dmesg while running thunderbird Gabriel C
2016-07-07 19:21 ` Chris Mason
2016-07-08 9:57 ` Gabriel C
2016-07-08 12:41 ` Chris Mason
2016-07-08 14:05 ` Gabriel C
2016-07-08 15:02 ` Gabriel C
2016-07-08 16:02 ` Chris Mason
2016-07-08 18:21 ` Adam Borowski
2016-07-08 21:47 ` Adam Borowski
2016-07-08 18:23 ` Duncan
2016-07-11 5:58 ` Chandan Rajendra
2016-07-11 10:51 ` Chris Mason
2016-07-19 11:05 ` Chris Mason
2016-07-20 0:11 ` Gabriel C
2016-07-20 13:50 ` Chris Mason
2016-07-20 17:50 ` Gabriel C
2016-07-21 12:56 ` Chris Mason
2016-07-21 21:25 ` Gabriel C
2016-07-22 0:53 ` Adam Borowski
2016-07-25 0:36 ` Dave Chinner
2016-08-01 15:23 ` Chris Mason
2016-07-15 19:35 ` Chris Mason
2016-07-15 21:08 ` Chris Mason [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=a17a5af4-cf5e-cb4e-de09-4aeb8282e891@fb.com \
--to=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nix.or.die@gmail.com \
--cc=quwenruo@cn.fujitsu.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).