linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Josef Bacik <jbacik@fb.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs soft lockups: locks gone crazy
Date: Fri, 17 Oct 2014 13:08:05 -0700	[thread overview]
Message-ID: <1413576485.22256.5.camel@linux-t7sj.site> (raw)
In-Reply-To: <54416EF6.1050403@fb.com>

On Fri, 2014-10-17 at 15:33 -0400, Josef Bacik wrote:
> On 10/14/2014 03:27 AM, Davidlohr Bueso wrote:
> > Hello,
> >
> > I'm getting massive amounts of cpu soft lockups in Linus's tree for
> > today. This occurs almost immediately and is very reproducible in aim7
> > disk workloads using btrfs:
> >
> 
> I'm trying to reproduce but it's not popping for me.  What is the setup 
> of your fs?  mkfs options, mount options etc.  And how are you running 
> aim7?  I'm using reaim with the default reaim.config and workfile,disk, 
> is this what you are using?  If not please attach your config and 
> workfile so I can be sure to be doing the same thing as you.  Thanks,

The steps I used are:

Download mmtests: https://github.com/gormanm/mmtests.git

cp configs/config-global-dhp__reaim-io config

edit the new config and just leave 'workfile.shared workfile.disk'
workloads as the REAIM_WORKFILES parameter.

./run-mmtests --no-monitor testname

Just a few mins into the test you should start getting the lockups. fwiw
I have not had the time to try other setups of reaim that are not
bundled with mmtests.

Thanks,
Davidlohr


      reply	other threads:[~2014-10-17 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14  7:27 btrfs soft lockups: locks gone crazy Davidlohr Bueso
2014-10-17 18:46 ` Davidlohr Bueso
2014-10-17 19:33 ` Josef Bacik
2014-10-17 20:08   ` Davidlohr Bueso [this message]

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=1413576485.22256.5.camel@linux-t7sj.site \
    --to=dave@stgolabs.net \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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).