From: Tomasz Chmielewski <tch@virtall.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel crashes with btrfs and busy database IO - how to debug?
Date: Sun, 14 Jun 2015 16:58:58 +0900 [thread overview]
Message-ID: <40998423616120fecd531f31971b0b8b@admin.virtall.com> (raw)
In-Reply-To: <f96134ed2c586f25fa959234fc525ab9@admin.virtall.com>
On 2015-06-14 09:30, Tomasz Chmielewski wrote:
> On 2015-06-13 08:23, Tomasz Chmielewski wrote:
>
>> I did get it from /var/crash/ though - is it more useful? I don't have
>> vmlinux for this kernel though, but have just built 4.1-rc7 with the
>> same config, can try to get the crash there.
>
> I've uploaded a crash dump and vmlinux here:
>
> http://www.virtall.com/files/temp/201506132321/
>
> Let me know if it's anything useful or if you need more info.
I've tried running it the same procedure to get one more crash, but it
didn't crash this time.
Instead, btrfs is hanged on any writes - any processes trying to write
get into D state and never return; there is no write activity when
checking for example with iostat. "sync" command does not return.
Reads from this btrfs filesystem are OK.
I've uploaded the output of "echo w > /proc/sysrq-trigger" here:
http://www.virtall.com/files/temp/dmesg.txt
Tomasz Chmielewski
next prev parent reply other threads:[~2015-06-14 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 11:33 kernel crashes with btrfs and busy database IO - how to debug? Tomasz Chmielewski
2015-06-12 7:13 ` Qu Wenruo
2015-06-12 8:35 ` Tomasz Chmielewski
2015-06-12 9:09 ` Qu Wenruo
2015-06-12 23:23 ` Tomasz Chmielewski
2015-06-14 0:30 ` Tomasz Chmielewski
2015-06-14 7:58 ` Tomasz Chmielewski [this message]
2015-06-15 8:10 ` Qu Wenruo
2015-06-15 10:31 ` Tomasz Chmielewski
2015-06-12 7:53 ` Duncan
2015-06-12 16:26 ` 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=40998423616120fecd531f31971b0b8b@admin.virtall.com \
--to=tch@virtall.com \
--cc=linux-btrfs@vger.kernel.org \
--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