From: Chris Mason <clm@fb.com>
To: Chandan Rajendra <chandan@linux.vnet.ibm.com>
Cc: Gabriel C <nix.or.die@gmail.com>, <linux-btrfs@vger.kernel.org>,
<quwenruo@cn.fujitsu.com>
Subject: Re: A lot warnings in dmesg while running thunderbird
Date: Mon, 11 Jul 2016 06:51:27 -0400 [thread overview]
Message-ID: <20160711105122.GA30104@clm-mbp.masoncoding.com> (raw)
In-Reply-To: <35812568.Zn4Yz0rfXf@localhost.localdomain>
On Mon, Jul 11, 2016 at 11:28:01AM +0530, Chandan Rajendra wrote:
>On Friday, July 08, 2016 12:02:35 PM Chris Mason wrote:
>>
>> Can you please run the attached test program:
>>
>> gcc -o short-write short-write.c -lpthread
>> ./short-write some-new-file-on-btrfs
>>
>> I want to see if you're triggering the same problem we've tried to fix,
>> or something else.
>>
>
>Hi Chris,
>
>I am able to reproduce the issue with the 'short-write' program. But before
>the call trace associated with btrfs_destroy_inode(), I see the following call
>trace ...
>
>------------[ cut here ]------------
>WARNING: CPU: 2 PID: 2311 at /home/chandan/repos/linux/fs/btrfs/extent-tree.c:4303 btrfs_free_reserved_data_space_noquota+0xe8/0x100
>Modules linked in:
[ ... ]
>
>I will continue to debug and find out the root cause.
Thanks Chandan, I'm able to reproduce the same thing more easily by changing
short-write to have:
#define ROUNDS 4096
and by getting rid of the sync_file_range call.
Still nailing down where the accounting is going wrong, so any help is
appreciated.
-chris
next prev parent reply other threads:[~2016-07-11 10:52 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 [this message]
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
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=20160711105122.GA30104@clm-mbp.masoncoding.com \
--to=clm@fb.com \
--cc=chandan@linux.vnet.ibm.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 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.