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 16:34:39 +0000 (UTC)
Subject: [Bug 42895] jbd2 makes all system unresponsive

--- Comment #13 from Eugene <>  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?).

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:

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:
------- 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