I used Eugenel's debugging method nr. 2 (find) and correlated it to the iotop outputs. The attached file includes listings of the recorded hard drive activity both while idling and while having Google Chrome open.
I think I may have identified the culprit in my case. What's common to all entries is hard drive writing activity in "/dev/ati/card0". if you look at the last intervall (15:25:30-15:26:40) you'll find that it's the only recorded change. Thus we can assume that most of the jbd2 I/O activity in the previous intervalls can be attributed to the same location. Two questions: 1.) Any idea why I can't access "/home/ari/.gvfs" despite being in a root shell? 2.) Does anyone know what "/dev/ati/card0" is used for? Can't open the file with gedit. Thank you in advance. ** Attachment added: "Time correlated outputs of find and iotop" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607560/+attachment/3271831/+files/iotop_and_find_correlated.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/607560 Title: jbd2 writing block every 5 - 10 seconds, preventing disk spin-down and making noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
