On Mon, Aug 25, 2014 at 2:08 AM, Holger Hoffstätte <holger.hoffstae...@googlemail.com> wrote: > On Sun, 24 Aug 2014 19:46:41 +0200, Flash ROM wrote: > >>> Happens a 100% of the time here, annoyingly. As mentioned, 3.15 was >>> working for me, and still does. Multiple reboots and it happens >>> immediately on boot even before gdm comes up. >> Would be logical to do block-level I/O tracing to get idea WHAT is this >> IO, right? > > Or you could just use proper tools for this: > > iotop: > http://guichaz.free.fr/iotop/
iotop already done, showed in the attached picture. I understand not all would want to load a pic, so the summary for iotop is that all the I/O is allocated to a kworker thread. The same attached picture also shows perf top for that pid, which I do not know how to interpret. https://db.tt/TSh5piq6 > > iosnoop: > http://www.brendangregg.com/blog/2014-07-16/iosnoop-for-linux.html > > Probably either a continuing balance or autodefrag vs. systemd's logging. Thank you, I'll try that out. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
