From: Josef Bacik <jbacik@fusionio.com>
To: Andrew McNabb <amcnabb@mcnabbs.org>
Cc: Josef Bacik <JBacik@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs stability
Date: Mon, 28 Jan 2013 09:17:23 -0500 [thread overview]
Message-ID: <20130128141723.GC3257@localhost.localdomain> (raw)
In-Reply-To: <20130126202711.GB30537@mcnabbs.org>
On Sat, Jan 26, 2013 at 01:27:11PM -0700, Andrew McNabb wrote:
> Here's an update. I tried the new kernel, and I seem to be having some
> new (possibly worse problems. In my ssh session, I'm seeing many errors
> of this sort:
>
> Message from syslogd@guru at Jan 26 13:13:14 ...
> kernel:[ 308.223834] BUG: soft lockup - CPU#0 stuck for 23s!
> [btrfs-endio-wri:2073]
>
> Message from syslogd@guru at Jan 26 13:13:14 ...
> kernel:[ 308.248754] BUG: soft lockup - CPU#2 stuck for 23s!
> [btrfs-delalloc-:594]
>
> In the logs, I'm seeing several warnings and bugs, including:
>
> WARNING: at fs/btrfs/extent_map.c:78 free_extent_map+0x79/0x90 [btrfs]()
> WARNING: at lib/list_debug.c:62 __list_del_entry+0x82/0xd0()
> BUG: unable to handle kernel NULL pointer dereference at (null)
> BUG: soft lockup - CPU#0 stuck for 22s! [btrfs-endio-wri:1489]
> BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-delalloc-:607]
>
> Kernel logs (across a few reboots) are at:
>
> http://students.cs.byu.edu/~amcnabb/messages2
>
Hrm well I didn't expect that. I will look into this and see what I can come up
with. Thanks,
Josef
next prev parent reply other threads:[~2013-01-28 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 20:05 btrfs stability Andrew McNabb
2013-01-25 20:37 ` Josef Bacik
2013-01-25 21:22 ` Andrew McNabb
2013-01-25 20:53 ` Josef Bacik
2013-01-25 21:39 ` Andrew McNabb
2013-01-26 20:27 ` Andrew McNabb
2013-01-28 14:17 ` Josef Bacik [this message]
2013-01-28 15:10 ` Josef Bacik
-- strict thread matches above, loose matches on Subject: below --
2016-05-26 22:42 Diego Torres
2016-05-27 5:14 ` Roman Mamedov
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=20130128141723.GC3257@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=amcnabb@mcnabbs.org \
--cc=linux-btrfs@vger.kernel.org \
/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).