I didn't see atime mentioned on the wiki page. Logging in fails for me right now (takes forever), so perhaps somebody else could add this info:
If you're looking for something that definitely does cause disk activity every 30 seconds, it's atime updates. When enabled (which they are by default), access times are updated for all file system _reads_ (even from the file system cache), and they are flushed very soon after (30 seconds AFAIK). If the problem really is that something is accessing the disk very often, atime is at least one of the most likely culprits. Mounting all filesystems noatime (or at least relatime) could make a big difference. Brian Visel wrote: > I'm 99% sure that the problem lies not (so much) in the aggressive APM, > but in the combination of the aggressive APM and some spurious constant > disk activity. If the disk activity weren't there, it wouldn't be so > much of an issue, and if the APM weren't so aggressive, it wouldn't be > so much of an issue. I'll notate this on the wiki. -- default value in power.sh potentially kills laptop disks https://bugs.launchpad.net/bugs/59695 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
