From: Chris Mason <chris.mason@oracle.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: Eric Whitney <eric.whitney@hp.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Updated performance results
Date: Wed, 16 Sep 2009 14:17:14 -0400 [thread overview]
Message-ID: <20090916181714.GF2641@think> (raw)
In-Reply-To: <4AB12B30.1020205@austin.ibm.com>
On Wed, Sep 16, 2009 at 01:15:12PM -0500, Steven Pratt wrote:
> Chris Mason wrote:
> >On Wed, Sep 16, 2009 at 12:57:22PM -0500, Steven Pratt wrote:
> >>Steven Pratt wrote:
> >>>Chris Mason wrote:
> >>>>On Mon, Sep 14, 2009 at 04:41:48PM -0500, Steven Pratt wrote:
> >>>>>Only bit of bad news is I did get one error that crashed the system
> >>>>>on single threaded nocow run. So that data point is missing.
> >>>>>Output below:
> >>>>I hope I've got this fixed. If you pull from the master branch of
> >>>>btrfs-unstable there are fixes for async thread races. The single
> >>>>patch I sent before is included, but not enough.
> >>>Glad you said that. Keeps me from sending the email that said the
> >>>patch didn't help :-)
> >>>
> >>>Steve
> >>Well, still getting oopses even with new code.
> >>
> >>Lots of:
> >>Sep 16 11:07:27 btrfs1 kernel: [ 1862.942754] BUG: soft lockup -
> >>CPU#10 stuck for 61s! [btrfs-endio-1:30250]
> >>Sep 16 11:07:27 btrfs1 kernel: [ 1862.942754] Pid: 30250, comm:
> >>btrfs-endio-1 Not tainted 2.6.31-autokern1 #1 IBM x3950-[88726RU]-
> >>Sep 16 11:07:27 btrfs1 kernel: [ 1862.942754] RIP:
> >>0010:[<ffffffff81153920>] [<ffffffff81153920>] crc32c+0x20/0x26
> >
> >If I'm reading this right, you've got a softlockup in crc32c? Something
> >has gone really wrong here. Are you reusing datasets from old runs?
> No, mkfs before every run.
Could you please send me the full softlockup output? Its hard to read
all line wrapped, so the original files would help.
-chris
next prev parent reply other threads:[~2009-09-16 18:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 18:35 Updated performance results Steven Pratt
2009-07-23 21:00 ` Chris Mason
2009-07-23 22:04 ` Steven Pratt
2009-07-24 13:24 ` Chris Mason
2009-07-24 14:00 ` Chris Mason
2009-07-24 15:05 ` Steven Pratt
2009-07-28 20:12 ` Steven Pratt
2009-07-28 20:23 ` Chris Mason
2009-07-28 21:10 ` Steven Pratt
2009-08-05 20:35 ` Chris Mason
2009-08-07 7:30 ` debian developer
2009-08-07 13:56 ` Steven Pratt
2009-08-07 13:56 ` Steven Pratt
2009-08-07 23:12 ` Chris Mason
2009-08-31 17:49 ` Steven Pratt
2009-09-11 19:29 ` Chris Mason
2009-09-11 21:35 ` Steven Pratt
2009-09-14 13:51 ` Chris Mason
2009-09-14 17:20 ` Jens Axboe
2009-09-14 21:41 ` Steven Pratt
2009-09-14 23:13 ` Chris Mason
2009-09-16 0:52 ` Chris Mason
2009-09-16 15:15 ` Steven Pratt
2009-09-16 17:57 ` Steven Pratt
2009-09-16 18:07 ` Chris Mason
2009-09-16 18:15 ` Steven Pratt
2009-09-16 18:17 ` Chris Mason [this message]
2009-09-16 18:16 ` Steven Pratt
2009-09-16 18:20 ` Chris Mason
2009-09-16 18:37 ` Steven Pratt
2009-09-17 18:32 ` Eric Whitney
2009-09-17 18:39 ` Steven Pratt
2009-09-17 18:52 ` Chris Mason
2009-09-17 20:17 ` Chris Mason
2009-09-17 20:43 ` Chris Mason
2009-09-17 22:04 ` Steven Pratt
2009-09-18 20:14 ` Chris Mason
2009-09-23 15:24 ` Steven Pratt
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=20090916181714.GF2641@think \
--to=chris.mason@oracle.com \
--cc=eric.whitney@hp.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=slpratt@austin.ibm.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