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 18:34:58 +0000 (UTC)	[thread overview]
Message-ID: <20120517183458.DB51F11FCF6@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42895-13602@https.bugzilla.kernel.org/>

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





--- Comment #17 from Theodore Tso <tytso@mit.edu>  2012-05-17 18:34:58 ---
Eugene,

I suspect this is much more of a change with the userspace components of the
distribution.  Ext3 hasn't changed much since 2.6.38, and everything I've said
about how jbd2 works also applies to ext3 and jbd.   So people who are
convinced this is a jbd2 problem can certainly try building a kernel with ext3
(for those distro's who are using ext4 for ext3 and ext4 file system formats).

My experience is that when comparing ext3 and ext4, I haven't found a situation
where ext4 has been slower than ext3.  If you can demonstrate a situation where
using ext3 you get one speed, and then using exactly the same configuration,
ext4 is slower, please let me know and we'll certainly take a look at it.

Something else you might try is dropping a modern (3.2 or 3.3) kernel unto an
older distribution.  I'm currently typing this on a Ubuntu LTS 10.04 system
running with a 3.2 kernel.  That would allow for a controlled experiment.  But
all I can say is if Network Manager is doing something as crazy as writing to a
Timestamp file every n seconds, there really is nothing you can do at the
kernel level.

-- 
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 18:35 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 [this message]
2012-05-17 20:02 ` bugzilla-daemon
2012-05-17 21:18 ` bugzilla-daemon
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=20120517183458.DB51F11FCF6@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).