All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Goodwin <david@codepoets.co.uk>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Periodic kernel freezes
Date: Fri, 30 Oct 2015 20:06:11 +0000	[thread overview]
Message-ID: <5633CDB3.2060905@codepoets.co.uk> (raw)
In-Reply-To: <63869607-1857-48D3-9D95-62BDBB308060@oseberg.io>


On 30/10/2015 16:25, Alex Adriaanse wrote:
> I have an EC2 instance on AWS that tends to freeze several times per
> week. When it freezes it stops responding to network traffic, disk
> I/O stops, and CPU goes to 100%. The system comes back fine after a
> reboot. I was finally able to get a kernel backtrace from when this
> happened today, which I have attached to this email.
>
> The VM in question runs Debian Jessie, and has 3 BTRFS filesystems,
> including the root filesystem. Details are included below.
>
> Any ideas?
>

Hi Alex -

I kept experiencing problems with the Jessie 3.16.x kernel on EC2 (and 
elsewhere) with BTRFS.

Out of 8 nodes, one managed an uptime of 90 days, while the average was 
about 21 days.

Crashes were seemingly random, and it was difficult to get stack traces.

For the stack traces I did get, it wasn't always obvious that the 
problem lay with BTRFS.

Reboots normally needed to be forceful.

I'd suggest upgrading to a backports kernel (I compiled various 4.1.x 
kernels, but there's now 4.2.x in jessie-backports).

You might also want to turn off compression...

David.

      reply	other threads:[~2015-10-30 20:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 16:25 Periodic kernel freezes Alex Adriaanse
2015-10-30 20:06 ` David Goodwin [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=5633CDB3.2060905@codepoets.co.uk \
    --to=david@codepoets.co.uk \
    --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.