linux-ext4 - [Bug 42895] jbd2 makes all system unresponsive

lists.openwall.net		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]

Message-Id: <20120516192954.B338211FCF6@bugzilla.kernel.org>
Date:	Wed, 16 May 2012 19:29:54 +0000 (UTC)
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 42895] jbd2 makes all system unresponsive

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





--- Comment #14 from Jan Kara <jack@...e.cz>  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
that.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html