From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 39072] jbd2 writes on disk every few seconds
Date: Mon, 11 Jul 2011 03:15:51 GMT [thread overview]
Message-ID: <201107110315.p6B3Fpl2024329@demeter1.kernel.org> (raw)
In-Reply-To: <bug-39072-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=39072
Lars Stokholm <lars.stokholm@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lars.stokholm@gmail.com
--- Comment #2 from Lars Stokholm <lars.stokholm@gmail.com> 2011-07-10 20:08:51 ---
I just wanted to say that I agree
--- Comment #3 from Lars Stokholm <lars.stokholm@gmail.com> 2011-07-10 20:13:38 ---
Oops. Sorry, I'm very new to this bug list, I committed before I should have.
I just wanted to say that I agree with you Theodore. Going into single user
mode helps. In fact just killing off my daemons (syslog-ng, cron and so on)
along with X was enough. I didn't have to go to single user mode.
--- Comment #4 from Theodore Tso <tytso@mit.edu> 2011-07-11 03:15:46 ---
Created an attachment (id=65212)
--> (https://bugzilla.kernel.org/attachment.cgi?id=65212)
Journal tracepoint patch
The following patch should help people figure out which process is responsible
for starting an jbd2 transaction handle. After applying the patch, enable it
via:
echo 1 > /sys/kernel/debug/tracing/events/ext4/ext4_journal_start/enable
echo 1 > /sys/kernel/debug/tracing/events/jbd2/jbd2_run_stats/enable
cat /sys/kernel/debug/tracing/trace_pipe
... and wait.
(All of this assumes you have ftrace enabled, of course).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2011-07-11 3:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 15:12 [Bug 39072] New: jbd2 writes on disk every few seconds bugzilla-daemon
2011-07-09 15:19 ` [Bug 39072] " bugzilla-daemon
2011-07-10 3:49 ` bugzilla-daemon
2011-07-11 3:15 ` bugzilla-daemon [this message]
2011-07-11 9:14 ` bugzilla-daemon
2011-07-11 9:21 ` bugzilla-daemon
2011-07-11 10:26 ` bugzilla-daemon
2011-07-11 10:49 ` bugzilla-daemon
2011-07-13 19:57 ` bugzilla-daemon
2011-07-14 17:02 ` bugzilla-daemon
2011-07-14 17:17 ` bugzilla-daemon
2011-07-14 17:25 ` bugzilla-daemon
2011-07-14 17:30 ` 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=201107110315.p6B3Fpl2024329@demeter1.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.