From: Florian Bruhin <me@the-compiler.org>
To: Filipe David Manana <fdmanana@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS critical / kernel BUG / high load
Date: Mon, 17 Mar 2014 13:47:09 +0100 [thread overview]
Message-ID: <20140317124708.GF21978@lupin> (raw)
In-Reply-To: <CAL3q7H6c5z7N6k0ixT+KN6+qfEzOMgrBOWQRX30vsfqSZoViTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
* Filipe David Manana <fdmanana@gmail.com> [2014-03-17 11:16:35 +0000]:
> On Mon, Mar 17, 2014 at 5:57 AM, Florian Bruhin <me@the-compiler.org> wrote:
> > Hi,
> >
> > on one of my servers running btrfs, I noticed a very high load of
> > 26/26/26. After investigating further, this happened in my logs about
> > 5 minutes before the monitoring alerted me because of the load:
>
> This issue was fixed in kernel 3.14 by:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5de865eebb8330eee19c37b31fb6f315a09d4273
>
> It was already backported to 3.12.14 but not yet to any 3.13 release.
Thanks, I see.
What about the free space error messages I got after the reboot?
Should I do anything or do I have to worry about anything being
corrupt? I'm running a scrub right now.
Florian
--
() ascii ribbon campaign - stop html mail www.asciiribbon.org
/\ www.the-compiler.org | I love long mails http://email.is-not-s.ms/
QOTD: "I haven't come far enough, and don't call me baby."
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-17 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 5:57 BTRFS critical / kernel BUG / high load Florian Bruhin
2014-03-17 10:47 ` Liu Bo
2014-03-17 10:59 ` Florian Bruhin
2014-03-17 11:16 ` Filipe David Manana
2014-03-17 12:47 ` Florian Bruhin [this message]
2014-03-17 13:08 ` Filipe David Manana
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=20140317124708.GF21978@lupin \
--to=me@the-compiler.org \
--cc=fdmanana@gmail.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.