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: Wed,  1 Aug 2012 02:43:13 +0000 (UTC)	[thread overview]
Message-ID: <20120801024313.5EE4511FC6C@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42895-13602@https.bugzilla.kernel.org/>

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





--- Comment #22 from Theodore Tso <tytso@mit.edu>  2012-08-01 02:43:12 ---
Nicolas,

The problem you are describing is not really related to the other problems (and
I use plural, because this bug has suffered from Ubuntu Launchpad disease ---
people are glomming onto a bug without understanding whether what they have are
the same bug or a different bug).

I don't know what is causing your freeze events, but by posting here, you're
only going to get the attention of ext4 developers.  The fact that you're not
seeing an exact correlation with jbd2 events means it's probably something
else.  The fact is that jbd2 activity is correlated with *any* change to the
file system.  So if you have something doing lots of unnecessary file system
writes, it's going to cause jbd2 activity.  That doesn't mean a jbd2 bug; it
just means the userspace is doing something unnecessary.

As far as your complaint is concerned, it's not at all obvious whether it's a
memory shortage problem, perhaps only in certain cgroup containers, or
something else entirely different.

I'm certainly not seeing any problems with my Debian wheezy laptop, but I'm
using Xfce, not GNOME 3, and I'm not using systemd.

-- 
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-08-01  2:43 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
2012-05-18 14:52 ` bugzilla-daemon
2012-07-30 20:00 ` bugzilla-daemon
2012-08-01  2:43 ` bugzilla-daemon [this message]
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=20120801024313.5EE4511FC6C@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).