Christian Vogler wrote: > Hum. I have noatime enabled, and as I mentioned in my (now disappeared) > comment on bug 59695, this did not make a difference for me. > > Here is my lm-profiler output: > > Profiling run started. > Write accesses at 72/600 in lm-profiler run: kpdf > Write accesses at 348/600 in lm-profiler run: kpdf > Read accesses at 599/600 in lm-profiler run: kblankscrn.kss kdesktop_lock > Profiling run completed. > > According to this run, the only possible culprit is kpdf. I shut it > down, but within 5 minutes, I saw the HDD LED flash several times, and > the load cycle count went up by 9. So, whatever is still accessing the > disk does not show up in lm-profiler, and is not due to atimes.
lm-profiler is useless if you look at the disk light / load cycles. It does a lot of its own stuff with the disk, so the disk activity you're seeing is most probably caused by lm-profiler itself. (It filters out this activity in the results, so you won't see it.) Simply put: lm-profiler is good for finding programs that do disk activity, but while you're using it you can't expect the disk to spin down. -- 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
