Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs panic - BUG: soft lockup - CPU#0 stuck for 61s!	[fs_mark:4573]
Date: Thu, 05 Jun 2008 11:16:26 -0400	[thread overview]
Message-ID: <4848034A.6090009@redhat.com> (raw)
In-Reply-To: <20080605143428.GA16999@think.oraclecorp.com>

Chris Mason wrote:
> On Mon, Jun 02, 2008 at 01:52:47PM -0400, Ric Wheeler wrote:
>   
>> I can reliably get btrfs to panic by running my fs_mark code on a newly  
>> created file system with lots of threads on an 8-way box. If this is too  
>> aggressive, let me know ;-)
>>
>> Here is a summary of the panic:
>>     
>
> BTW, exactly how are you running fs_mark?  Mingming reminded me that
> strictly speaking this patch shouldn't be required, so there might be
> other related problems.
>
> -chris
>
>   
This was the actual command:

./fs_mark -d /mnt/test -D 512 -t 16 -s 409600 -F

I will give your patch a spin right after lunch ;-)

ric



  reply	other threads:[~2008-06-05 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 17:52 btrfs panic - BUG: soft lockup - CPU#0 stuck for 61s! [fs_mark:4573] Ric Wheeler
2008-06-04  1:27 ` Chris Mason
2008-06-04 19:46   ` Ric Wheeler
2008-06-04 20:12     ` Chris Mason
2008-06-05 14:34 ` Chris Mason
2008-06-05 15:16   ` Ric Wheeler [this message]
     [not found]   ` <484825D4.2010402@redhat.com>
2008-06-09  2:37     ` Chris Mason
2008-06-09 13:51       ` Ric Wheeler
2008-06-10  0:10       ` Mingming Cao
2008-06-10  0:47         ` Chris Mason
2008-06-10 18:38           ` Mingming Cao

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=4848034A.6090009@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=chris.mason@oracle.com \
    --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