Groover wrote: >> ubuntu_demon wrote: >> I would like to see some btrace output from people who are suffering from >> the fastly increasing Load_Cycle_Count problem. > > Indeed, it was interesting! I have had evolution running on another > workspace, but it had not touched the drive. Instead, it were kjournald > and pdflush. I have left the laptop idle for 5 minutes with three > programs open (well, those I don't have in auto startup): Evolution, > Gnome-terminal and Pidgin.
Note that kjournald and pdflush are kernel processes that write "expired" data out to disk. To be precise, pdflush writes the data, and kjournald does the ext3 journalling. This means that some processes that you were running modified files earlier on, and then pdflush writes them to disk 30 seconds later. Enable /proc/sys/vm/block_dump and check your dmesg output to tell you when processes actually modify which files! (But remember to _disable syslogd_ while you do this!) -- Hard drive spindown should be configurable https://bugs.launchpad.net/bugs/17216 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
