lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 16 May 2012 19:29:54 +0000 (UTC)
Subject: [Bug 42895] jbd2 makes all system unresponsive

--- Comment #14 from Jan Kara <>  2012-05-16 19:29:54 ---
I've looked at the results and they look normal. Different processes dirty some
inodes - after a while jbd2 journal thread writes these changes to the journal
(it checks once per 5s). The journal thread writes somewhat more because there
are some descriptor blocks etc.

Also once per 5s, flusher wakes up and writes all dirty data older than 30s.

So really sources of all the activity are those few processes (gedit,
NetworkManager, xfconfd) which do dirtying and the rest is just triggered by

Configure bugmail:
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists