linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42895] jbd2 makes all system unresponsive
Date: Thu, 17 May 2012 21:18:25 +0000 (UTC)	[thread overview]
Message-ID: <20120517211825.DD9BC11FCF6@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42895-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=42895


Sami Liedes <sliedes@cc.hut.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sliedes@cc.hut.fi




--- Comment #19 from Sami Liedes <sliedes@cc.hut.fi>  2012-05-17 21:18:25 ---
I have seen this too; basically latencies have always been a problem with KDE
(at least KDE 4) on ext4, as far as I can tell. Switching to XFS solved the
problem for me.

One thing I might be able to add to the discussion:

While this problem manifests without disk crypto, adding dm-crypt to the soup,
especially on a computer _without_ hardware AES support, generally makes it
*much* worse. I've seen disk accesses, especially fsync()s (per latencytop),
take minutes in the worst case under some medium disk load; 5-10 seconds are a
norm on light I/O load. I can't see much reason why disk crypto should make it
that much slower. But since it's a problem also without crypto, perhaps
dm-crypt just somehow makes it worse and more obvious?

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-05-17 21:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 10:42 [Bug 42895] New: jbd2 makes all system unresponsive bugzilla-daemon
2012-03-09 10:49 ` [Bug 42895] " bugzilla-daemon
2012-05-02 12:10 ` bugzilla-daemon
2012-05-02 16:08 ` bugzilla-daemon
2012-05-02 16:10 ` bugzilla-daemon
2012-05-02 18:49 ` bugzilla-daemon
2012-05-02 19:50 ` bugzilla-daemon
2012-05-05 20:42 ` bugzilla-daemon
2012-05-13 15:30 ` bugzilla-daemon
2012-05-14 10:44 ` bugzilla-daemon
2012-05-14 21:43 ` bugzilla-daemon
2012-05-15 14:40 ` bugzilla-daemon
2012-05-15 14:54 ` bugzilla-daemon
2012-05-16 16:34 ` bugzilla-daemon
2012-05-16 19:29 ` bugzilla-daemon
2012-05-16 20:24 ` bugzilla-daemon
2012-05-17 16:34 ` bugzilla-daemon
2012-05-17 18:34 ` bugzilla-daemon
2012-05-17 20:02 ` bugzilla-daemon
2012-05-17 21:18 ` bugzilla-daemon [this message]
2012-05-18 14:52 ` bugzilla-daemon
2012-07-30 20:00 ` bugzilla-daemon
2012-08-01  2:43 ` bugzilla-daemon
2012-08-01  2:45 ` bugzilla-daemon

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=20120517211825.DD9BC11FCF6@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).