https://bugzilla.kernel.org/show_bug.cgi?id=42895 --- Comment #6 from Theodore Tso <tytso@xxxxxxx> 2012-05-02 19:50:49 --- As I expected, this is being caused by some application --- it looks like Chrome's DB thread, is calling fsync() very aggressively. If you exit your Chrome browser, it should cause your disk from being used all the time. I suspect the new kernel and the use of ext4 was just a coincidence. Since I'm using the very latest Chrome 19 beta and I'm not seeing this, I'm going to guess that it's some Chrome extension, or some page which you are visiting that is causing the large amounts of fsync() activity. You can get a continuous reading of fsync() activity by enabling the above tracepoint, and then in a window, running the command "cat /sys/kernel/debug/tracing/trace_pipe". If the fsync() activity goes away after you exit the Chrome browser, try starting up the Chrome browser and then see if you see the heavy fsync() activity with just a empty browser window before you start opening lots and lots of tabs. Also try disabling all of your Chrome extensions, and see if that quiet things done. Once you get things quiet, try enabling Chrome extensions one at a time, and opening various web pages one at a time, and see if you can figure out what causes the fsync storm. It may very well be some flash-enabled page --- I run with FlashControl to take out potential web page malware, or other things that I don't want (and which can often burn CPU time and hence battery life). Cheers, -- 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
