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: Wed, 16 May 2012 16:34:39 +0000 (UTC)	[thread overview]
Message-ID: <20120516163439.916CD11FCF6@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42895-13602@https.bugzilla.kernel.org/>

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





--- Comment #13 from Eugene <ivanovstm2@zmail.ru>  2012-05-16 16:34:39 ---
Thanks, now it works.
Traced system for around 10mins and I don't see previously unseen processes.
Just normal system activity. But there was a number of hdd writes (around 6 in
10mins) which doesn't have corresponding entries in trace results and separated
from entries by roughly 30sec (flush?) - that's not including 1-2 writes
closely following (~3-5sec) almost each entry (jbd2?).
http://paste.ubuntu.com/990927/

Can I trace some function which gives output in trace results when actual write
takes place but shows initial cause of the write (not just flush or jbd2)? Like
block_dump but more informative?

If it's not possible then for now I'm going to presume that it's just the way
how system works. But still it's lots of flushes/jbd2 following writes of even
small files:
https://launchpadlibrarian.net/101378473/15mins_almost_idle.txt

For example in above block_dump Network Manager's "timestamps" file is 4910
bytes long and followed by ~20 writes by jbd2 and then by 10 flushes.
Or xfconfd's "xfce4-panel.xml" is 9467 bytes long and followed by 8 writes by
jbd2 and then by 20 flushes all around the disk.
Is it normal?

-- 
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-16 16:34 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 [this message]
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=20120516163439.916CD11FCF6@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.