All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Schmid <schmid@phys.ethz.ch>
To: Chris Mason <clm@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: soft lockup - CPU#0 stuck - Kernel 3.17.2
Date: Thu, 13 Nov 2014 20:07:18 +0100	[thread overview]
Message-ID: <54650166.1090800@phys.ethz.ch> (raw)
In-Reply-To: <1415890157.25389.3@mail.thefacebook.com>

On 11/13/2014 03:49 PM, Chris Mason wrote:
>
>
> On Thu, Nov 13, 2014 at 8:32 AM, Patrick Schmid <schmid@phys.ethz.ch>
> wrote:
>> Hi all,
>>
>> we run a > 500 TiB backup system on iSCSI targets using 19 BTRFS
>> filesystems (the biggest of which is 110 TiB) on Ubuntu 14.04 LTS and
>> various kernel versions. Btrfs-Progs v3.17.1. The hardware is a 24
>> core
>> Xeon E5-2620 on an Intel S2600GZ board with 128 GiB RAM.
>>
>> Since btrfs has changed to kworkers (I think in 3.15) the frontend
>> server somewhat randomly crashes with soft lockups (see attachment).
>> The
>> system is rock solid with the 3.14.22 kernel.
>>
>> The lockups happen during the nightly cron-controlled rsync backups
>> and
>> occur at random times during this process.
>> We are totally aware of the fact that this tends to be one of
>> those “it doesn’t work” bug reports, but
>> it’s really hard to pin
>> down the source of the problem other than it seems to be related to
>> the
>> kworkers. We’d love to provide any feedback we can, please let
>> us know
>> what you need.
>
> Hi,
>
> This may actually be related to a different btrfs change in the 3.15
> kernel.  Do you see more than one soft lockup?  After the softlockup,
> does the box recover or is it stuck forever?
>
> -chris
>

Hi Chris

"Normaly" are there more than one soft lockup and the load goes up to 
sky and the server stuck forever until hard reset.

If you want, i send you tomorrow morning the whole kernel log?

regards
Patrick

  reply	other threads:[~2014-11-13 19:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 13:32 soft lockup - CPU#0 stuck - Kernel 3.17.2 Patrick Schmid
2014-11-13 14:49 ` Chris Mason
2014-11-13 19:07   ` Patrick Schmid [this message]
2014-11-13 19:12     ` Chris Mason
     [not found]       ` <54659FDB.6070300@phys.ethz.ch>
2014-11-14 17:39         ` Chris Mason
2014-11-14 18:23           ` Patrick Schmid
2014-11-14 18:31             ` Chris Mason
2014-11-14 23:47               ` Chris Mason
2014-11-21 13:01                 ` Patrick Schmid
2014-11-21 13:16                   ` Chris Mason

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=54650166.1090800@phys.ethz.ch \
    --to=schmid@phys.ethz.ch \
    --cc=clm@fb.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 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.