All of lore.kernel.org
 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: Sun, 13 May 2012 15:30:31 +0000 (UTC)	[thread overview]
Message-ID: <20120513153031.7EB4111FCE2@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42895-13602@https.bugzilla.kernel.org/>

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





--- Comment #8 from Eugene <ivanovstm2@zmail.ru>  2012-05-13 15:30:31 ---
There's related jbd2 bug in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607560 - ext4 jbd2 writing
block every 5-10 seconds, preventing disk spin-down and making noise. Even when
PC is idle.
Bug report open 2010.08 and still active; includes newest Ubuntu 12.04.
+ half a dozen of threads on Ubuntu and Archlinux forums including thread for
this bug:
https://bbs.archlinux.org/viewtopic.php?id=139087 - Intense disk IO (jbd2 and
flush) blocks user interface.

I personally not sure that this is jbd2's fault. Something must be going on in
the system. The problem is that nobody is able to point a finger at the cause
except that jbd2 writes to disk.


Following instructions given by Theodore Ts'O, I don't see excessive usage of
fsync:
http://paste.ubuntu.com/981398

block_dump of my idle system doesn't shows something out of ordinary except
much of flush/jbd2 activity:
http://paste.ubuntu.com/983568/
(sda3 /, sda6 /home. Network Manager writes every 5min, xfconfd - every 10min;
open apps - terminal, gedit, xfce thunar and light screensaver; syslog
disabled).

When I watch /proc/meminfo "Dirty:" field, it shows that during and *following*
any system activity - memory being dirtied ~every 3-15 seconds (accompanied
with audible HDD clicks) and flushed to disk. This goes on for some time then
all quietens.
"iotop" shows jbd2 writes and writes of process which it can't properly
recognize.


Is there a way to find a cause of flush and jbd2 writes? Like apllication name
or PID?
Preferably without need to patch/compile new kernel, so that as many people as
possible can use it.


P.S. Subjective feeling is that any work done on system (and often idling too)
no matter how light is accompanied by noticeable HDD clicks every ~5sec. And
opening even relatively light apps like gedit leads to bursts of loud HDD
usage.

-- 
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-13 15:30 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 [this message]
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
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=20120513153031.7EB4111FCE2@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 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.