There is something that I don't understand. As listed above, there are activity on both partitions, root and home. It seems difficult to know what file is really written by jdb2 process (logs ?), so it's difficult to know for what application or thread those IO are done. Moreover, we can see some activity that doesn't result in any read or write (0.00 B/s in DISK READ, and 0.00 B/s in DISK WRITE). So, what does jdb2 at this moment that could looks like an IO for iotop ? What could explain that jdb2 doesn't respect the commit interval for everyone ?
If someone could made a brief summary of what is known about this jdb2 process, it will be helpful in order to build more tries to isolate the process or the file that takes the most amount of IO. -- 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
