From: Chris Mason <chris.mason@oracle.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>,
"Chen, Tim C" <tim.c.chen@intel.com>
Subject: Re: btrfs caused kernel oops warning
Date: Wed, 22 Sep 2010 08:13:11 -0400 [thread overview]
Message-ID: <20100922121311.GD2309@think> (raw)
In-Reply-To: <1284691538.30133.9.camel@sli10-conroe.sh.intel.com>
On Fri, Sep 17, 2010 at 10:45:38AM +0800, Shaohua Li wrote:
> Chris,
> we are seeing kernel warning from time to time when doing btrfs test.
> That issue is hard to trigger, but it sometimes pop up. we saw this in
> both fio and ffsb test in several kernel version. Below is an example.
> do you have idea about it? we are glad to test patches/do debug if you
> can share some ideas.
Interesting. We're backing up behind the ordered operations mutex, but
I don't see the stack trace from the process currently holding it.
Could you please do a sysrq-w and record the results? We need to see
who we are stuck on.
My guess is we're stuck waiting for IO, but the traces will say for
sure.
-chris
parent reply other threads:[~2010-09-22 12:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1284691538.30133.9.camel@sli10-conroe.sh.intel.com>]
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=20100922121311.GD2309@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=tim.c.chen@intel.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.