NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Stoffen
Feb 25, 2014Aspirant
RN104 - process "find" uses 100% cpu for several hours
Hi. Hopefully some of you might be able to help me here :) I have a ReadyNAS 104 with version 6.1.6 I have installed Cacti service to monitor my NAS and some other devices on my LAN. Several...
Stoffen
Mar 02, 2014Aspirant
I somewhat found a solution, or lowered the number of hours "find" runs in the system.
I modified the file /etc/cron.daily/locate
In the file, I pruned the following:
PRUNEPATHS="/data/._share/Documents/.snapshot/ ./data/._share/Music/.snapshot/ ./data/._share/Pictures/.snapshot/" as well as the original pruned paths.
This refers to my shares, of which I know contains alot of data.
The next time locate ran, it did the entire find and locate thingie in 10 hours insted of 23 or so..
I still feel that this is the wrong approach to the problem, but it seems indeed as the problem is within "locate"'s daily rutine in the combination of the way ReadyNas 104 creates shapshots.
More good ideas is more than welcome :)
I modified the file /etc/cron.daily/locate
In the file, I pruned the following:
PRUNEPATHS="/data/._share/Documents/.snapshot/ ./data/._share/Music/.snapshot/ ./data/._share/Pictures/.snapshot/" as well as the original pruned paths.
This refers to my shares, of which I know contains alot of data.
The next time locate ran, it did the entire find and locate thingie in 10 hours insted of 23 or so..
I still feel that this is the wrong approach to the problem, but it seems indeed as the problem is within "locate"'s daily rutine in the combination of the way ReadyNas 104 creates shapshots.
More good ideas is more than welcome :)
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!