Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: [BUG] [4.1-rc4] hung tasks on resume
Date: Sun, 24 May 2015 11:46:15 +0200	[thread overview]
Message-ID: <38718451.QrrZiIAI7Z@merkaba> (raw)

Hi!

I had another BTRFS hang¹. It may be related to the kworker at 100% on write 
issue that still happened with 4.0 kernels² as / device was 100% allocated 
and it seems that bug doesn´t happen if there is still device space left to 
be allocated for chunks.

But this time it was on resume from hibernation. All I could get was a 
backtrace on the console.


IMHO this still is not production ready, despite any other sayings.


[1] [Bug 98821] New: btrfs hung tasks on resume from hibernation
https://bugzilla.kernel.org/show_bug.cgi?id=98821

[2] [Bug 90401] New: btrfs kworker thread uses up 100% of a Sandybridge core 
for minutes on random write into big file
https://bugzilla.kernel.org/show_bug.cgi?id=90401

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

                 reply	other threads:[~2015-05-24  9:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=38718451.QrrZiIAI7Z@merkaba \
    --to=martin@lichtvoll.de \
    --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