I have this problem too and I have a question about Necs comment with reads:
" Hi, I found out that playing with ionice nor nice did not improve anything in that case. (that also was VERY severe to me) The issue came from the fact that my computer mounts some remote filesystems, and find and locate went exploring those distant folders. I solved the problem by changing /etc/cron.daily/locate and adding the "xdev" options to the find parameters. # Global options for invocations of find(1) FINDOPTIONS='-ignore_readdir_race -xdev' Now, updates are still relevent, but cause no CPU harm nor wasted time :) " First I dont have a /etc/cron.daily/locate on 14.10 and I have only a /mlocate and there is no find command in there so I guess I can't cry to fix it this way? Or should I just and the FINDOPTIONS line in there? I guess I will completely disable the cronjob for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190696 Title: updatedb.mlocate uses 100% of the hdd IO. The OS is completely unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1190696/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
