All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 39072] jbd2 writes on disk every few seconds
Date: Thu, 14 Jul 2011 17:02:50 GMT	[thread overview]
Message-ID: <201107141702.p6EH2o34019830@demeter1.kernel.org> (raw)
In-Reply-To: <bug-39072-13602@https.bugzilla.kernel.org/>

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


mkkot <marcin2006@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #10 from mkkot <marcin2006@gmail.com>  2011-07-14 17:02:39 ---
After 5 and half hour of compilation ;) I have some results:

- command sysctl vm.block_dump=1 (so I can see writes and reads with dmesg |
grep -e READ -e WRITE) makes syslog-ng to write every few seconds which
triggers jbd2 as well. So I fell in my own trap. Killing syslog helps there.

- console-kit-daemon also triggers jbd2. I'm not sure why but it writes over
and over again in text-mode. Killing it helps until you log in within another
console, then it starts again. It quiets in X mode, though. Strange.

- Killing console-kit-daemon in text-mode enables possibility to spin-down the
disk for a minute or two. Then some pdflush or cron job starts.

So it seems there is nothing wrong with ext4. Anyway, thanks for the patch, it
was very helpful to determine what is wrong and solve people's problems.

-- 
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:[~2011-07-14 17:02 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
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 [this message]
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=201107141702.p6EH2o34019830@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.