sacretagent Posted August 21, 2013 Share Posted August 21, 2013 I ran into similar issue a while back running cachedirs verbose tells you which disk is holding up the process what i did is move a bunch of music mp3's to a disk which was only holding big files and that also solved the issue i also once had some small filesystem error keeping cachedirs busy... i only realized once i did a parity check and the disk gave like 3 errors run reiserfsck solved that at that time Quote Link to comment
Eisi2005 Posted September 14, 2013 Share Posted September 14, 2013 @Joe L. sine tonight i have this entries in my logfile. Running unraid 5.0 Sep 13 23:26:25 Server cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 9999 -p 10 -a "-noleaf" Sep 13 23:27:00 Server cache_dirs: ============================================== Sep 13 23:27:00 Server cache_dirs: command-args=-w -m 1 -M 10 -d 9999 -p 10 -a -noleaf Sep 13 23:27:00 Server cache_dirs: vfs_cache_pressure=10 Sep 13 23:27:00 Server cache_dirs: max_seconds=10, min_seconds=1 Sep 13 23:27:00 Server cache_dirs: max_depth=9999 Sep 13 23:27:00 Server cache_dirs: command=find -noleaf Sep 13 23:27:00 Server cache_dirs: version=1.6.7 Sep 13 23:27:00 Server cache_dirs: ---------- caching directories --------------- Sep 13 23:27:00 Server cache_dirs: server Sep 13 23:27:00 Server cache_dirs: ---------------------------------------------- Sep 13 23:27:00 Server cache_dirs: cache_dirs process ID 24124 started, To terminate it, type: cache_dirs -q From where did these entries come ? I have only normaly started cache_dirs -w at startup ? Eisi syslog-2013-09-14.zip Quote Link to comment
Joe L. Posted September 14, 2013 Author Share Posted September 14, 2013 @Joe L. sine tonight i have this entries in my logfile. Running unraid 5.0 Sep 13 23:26:25 Server cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 9999 -p 10 -a "-noleaf" Sep 13 23:27:00 Server cache_dirs: ============================================== Sep 13 23:27:00 Server cache_dirs: command-args=-w -m 1 -M 10 -d 9999 -p 10 -a -noleaf Sep 13 23:27:00 Server cache_dirs: vfs_cache_pressure=10 Sep 13 23:27:00 Server cache_dirs: max_seconds=10, min_seconds=1 Sep 13 23:27:00 Server cache_dirs: max_depth=9999 Sep 13 23:27:00 Server cache_dirs: command=find -noleaf Sep 13 23:27:00 Server cache_dirs: version=1.6.7 Sep 13 23:27:00 Server cache_dirs: ---------- caching directories --------------- Sep 13 23:27:00 Server cache_dirs: server Sep 13 23:27:00 Server cache_dirs: ---------------------------------------------- Sep 13 23:27:00 Server cache_dirs: cache_dirs process ID 24124 started, To terminate it, type: cache_dirs -q From where did these entries come ? I have only normaly started cache_dirs -w at startup ? Eisi If the array is off-line, cache_dirs will re-schedule itself to be run when the array is possibly online. The log entry is entirely normal when this ccurs. Quote Link to comment
Eisi2005 Posted September 14, 2013 Share Posted September 14, 2013 @Joe thanks for your answer, but to the times where cache_dirs started, the array was not offline. Eisi Quote Link to comment
spants Posted October 16, 2013 Share Posted October 16, 2013 I have just started getting the same in my logs: Oct 15 22:25:04 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 15 22:26:00 Tower cache_dirs: ============================================== Oct 15 22:26:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 15 22:26:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 15 22:26:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 15 22:26:00 Tower cache_dirs: max_depth=4 Oct 15 22:26:00 Tower cache_dirs: command=find -noleaf Oct 15 22:26:00 Tower cache_dirs: version=1.6.5 Oct 15 22:26:00 Tower cache_dirs: ---------- caching directories --------------- Oct 15 22:26:00 Tower cache_dirs: Videos Oct 15 22:26:00 Tower cache_dirs: ---------------------------------------------- Oct 15 22:26:00 Tower cache_dirs: cache_dirs process ID 4369 started, To terminate it, type: cache_dirs -q Oct 15 22:27:48 Tower kernel: mdcmd (203): spindown 0 (Routine) Oct 15 22:27:48 Tower kernel: mdcmd (204): spindown 2 (Routine) Oct 15 23:19:49 Tower kernel: mdcmd (205): spindown 4 (Routine) Oct 15 23:20:00 Tower kernel: mdcmd (206): spindown 1 (Routine) Oct 15 23:20:00 Tower kernel: mdcmd (207): spindown 2 (Routine) Oct 15 23:20:00 Tower kernel: mdcmd (208): spindown 3 (Routine) Oct 15 23:20:01 Tower kernel: mdcmd (209): spindown 5 (Routine) Oct 15 23:20:01 Tower kernel: mdcmd (210): spindown 6 (Routine) Oct 15 23:20:51 Tower kernel: mdcmd (211): spindown 7 (Routine) Oct 15 23:50:02 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 15 23:51:00 Tower cache_dirs: ============================================== Oct 15 23:51:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 15 23:51:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 15 23:51:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 15 23:51:00 Tower cache_dirs: max_depth=4 Oct 15 23:51:00 Tower cache_dirs: command=find -noleaf Oct 15 23:51:00 Tower cache_dirs: version=1.6.5 Oct 15 23:51:00 Tower cache_dirs: ---------- caching directories --------------- Oct 15 23:51:00 Tower cache_dirs: Videos Oct 15 23:51:00 Tower cache_dirs: ---------------------------------------------- Oct 15 23:51:00 Tower cache_dirs: cache_dirs process ID 30794 started, To terminate it, type: cache_dirs -q Oct 16 01:14:29 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 01:15:01 Tower cache_dirs: ============================================== Oct 16 01:15:01 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 01:15:01 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 01:15:01 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 01:15:01 Tower cache_dirs: max_depth=4 Oct 16 01:15:01 Tower cache_dirs: command=find -noleaf Oct 16 01:15:01 Tower cache_dirs: version=1.6.5 Oct 16 01:15:01 Tower cache_dirs: ---------- caching directories --------------- Oct 16 01:15:01 Tower cache_dirs: Videos Oct 16 01:15:01 Tower cache_dirs: ---------------------------------------------- Oct 16 01:15:01 Tower cache_dirs: cache_dirs process ID 24715 started, To terminate it, type: cache_dirs -q Oct 16 02:17:13 Tower kernel: mdcmd (212): spindown 0 (Routine) Oct 16 02:17:14 Tower kernel: mdcmd (213): spindown 1 (Routine) Oct 16 02:41:06 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 02:42:00 Tower cache_dirs: ============================================== Oct 16 02:42:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 02:42:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 02:42:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 02:42:00 Tower cache_dirs: max_depth=4 Oct 16 02:42:00 Tower cache_dirs: command=find -noleaf Oct 16 02:42:00 Tower cache_dirs: version=1.6.5 Oct 16 02:42:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 02:42:00 Tower cache_dirs: Videos Oct 16 02:42:00 Tower cache_dirs: ---------------------------------------------- Oct 16 02:42:00 Tower cache_dirs: cache_dirs process ID 18694 started, To terminate it, type: cache_dirs -q Oct 16 03:15:45 Tower kernel: mdcmd (214): spindown 0 (Routine) Oct 16 03:15:45 Tower kernel: mdcmd (215): spindown 1 (Routine) Oct 16 03:16:16 Tower kernel: mdcmd (216): spindown 2 (Routine) Oct 16 03:29:26 Tower kernel: mdcmd (217): spindown 3 (Routine) Oct 16 04:02:47 Tower kernel: mdcmd (218): spindown 3 (Routine) Oct 16 04:02:57 Tower kernel: mdcmd (219): spindown 4 (Routine) Oct 16 04:03:07 Tower kernel: mdcmd (220): spindown 5 (Routine) Oct 16 04:04:17 Tower kernel: mdcmd (221): spindown 7 (Routine) Oct 16 04:05:28 Tower kernel: mdcmd (222): spindown 2 (Routine) Oct 16 04:07:38 Tower kernel: mdcmd (223): spindown 1 (Routine) Oct 16 04:08:49 Tower kernel: mdcmd (224): spindown 6 (Routine) Oct 16 04:37:39 Tower kernel: mdcmd (225): spindown 1 (Routine) Oct 16 04:40:02 Tower su[13762]: Successful su for unraid-plex by root Oct 16 04:40:02 Tower su[13762]: + root:unraid-plex Oct 16 04:44:23 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 04:45:00 Tower cache_dirs: ============================================== Oct 16 04:45:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 04:45:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 04:45:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 04:45:00 Tower cache_dirs: max_depth=4 Oct 16 04:45:00 Tower cache_dirs: command=find -noleaf Oct 16 04:45:00 Tower cache_dirs: version=1.6.5 Oct 16 04:45:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 04:45:00 Tower cache_dirs: Videos Oct 16 04:45:00 Tower cache_dirs: ---------------------------------------------- Oct 16 04:45:00 Tower cache_dirs: cache_dirs process ID 14478 started, To terminate it, type: cache_dirs -q Oct 16 04:57:50 Tower kernel: mdcmd (226): spindown 3 (Routine) Oct 16 04:58:00 Tower kernel: mdcmd (227): spindown 5 (Routine) Oct 16 04:58:00 Tower kernel: mdcmd (228): spindown 6 (Routine) Oct 16 04:58:01 Tower kernel: mdcmd (229): spindown 7 (Routine) Oct 16 05:16:51 Tower kernel: mdcmd (230): spindown 1 (Routine) Oct 16 05:17:12 Tower kernel: mdcmd (231): spindown 4 (Routine) Oct 16 05:17:42 Tower kernel: mdcmd (232): spindown 6 (Routine) Oct 16 05:29:13 Tower kernel: mdcmd (233): spindown 2 (Routine) Oct 16 05:33:33 Tower kernel: mdcmd (234): spindown 3 (Routine) Oct 16 05:33:33 Tower kernel: mdcmd (235): spindown 5 (Routine) Oct 16 05:33:33 Tower kernel: mdcmd (236): spindown 7 (Routine) Oct 16 06:28:54 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 06:29:00 Tower cache_dirs: ============================================== Oct 16 06:29:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 06:29:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 06:29:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 06:29:00 Tower cache_dirs: max_depth=4 Oct 16 06:29:00 Tower cache_dirs: command=find -noleaf Oct 16 06:29:00 Tower cache_dirs: version=1.6.5 Oct 16 06:29:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 06:29:00 Tower cache_dirs: Videos Oct 16 06:29:00 Tower cache_dirs: ---------------------------------------------- Oct 16 06:29:00 Tower cache_dirs: cache_dirs process ID 8556 started, To terminate it, type: cache_dirs -q Oct 16 07:58:46 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 07:59:01 Tower cache_dirs: ============================================== Oct 16 07:59:01 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 07:59:01 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 07:59:01 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 07:59:01 Tower cache_dirs: max_depth=4 Oct 16 07:59:01 Tower cache_dirs: command=find -noleaf Oct 16 07:59:01 Tower cache_dirs: version=1.6.5 Oct 16 07:59:01 Tower cache_dirs: ---------- caching directories --------------- Oct 16 07:59:01 Tower cache_dirs: Videos Oct 16 07:59:01 Tower cache_dirs: ---------------------------------------------- Oct 16 07:59:01 Tower cache_dirs: cache_dirs process ID 2527 started, To terminate it, type: cache_dirs -q Oct 16 09:06:45 Tower kernel: mdcmd (237): spindown 3 (Routine) Oct 16 09:26:56 Tower kernel: mdcmd (238): spindown 2 (Routine) Oct 16 09:44:46 Tower kernel: mdcmd (239): spindown 2 (Routine) Oct 16 09:57:04 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 09:58:00 Tower cache_dirs: ============================================== Oct 16 09:58:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 09:58:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 09:58:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 09:58:00 Tower cache_dirs: max_depth=4 Oct 16 09:58:00 Tower cache_dirs: command=find -noleaf Oct 16 09:58:00 Tower cache_dirs: version=1.6.5 Oct 16 09:58:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 09:58:00 Tower cache_dirs: Videos Oct 16 09:58:00 Tower cache_dirs: ---------------------------------------------- Oct 16 09:58:00 Tower cache_dirs: cache_dirs process ID 29209 started, To terminate it, type: cache_dirs -q Oct 16 10:32:17 Tower kernel: mdcmd (240): spindown 2 (Routine) Oct 16 11:02:08 Tower kernel: mdcmd (241): spindown 2 (Routine) Oct 16 11:02:08 Tower kernel: mdcmd (242): spindown 7 (Routine) Oct 16 11:14:34 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 11:15:01 Tower cache_dirs: ============================================== Oct 16 11:15:01 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 11:15:01 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 11:15:01 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 11:15:01 Tower cache_dirs: max_depth=4 Oct 16 11:15:01 Tower cache_dirs: command=find -noleaf Oct 16 11:15:01 Tower cache_dirs: version=1.6.5 Oct 16 11:15:01 Tower cache_dirs: ---------- caching directories --------------- Oct 16 11:15:01 Tower cache_dirs: Videos Oct 16 11:15:01 Tower cache_dirs: ---------------------------------------------- Oct 16 11:15:01 Tower cache_dirs: cache_dirs process ID 23174 started, To terminate it, type: cache_dirs -q Oct 16 12:32:57 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 12:33:00 Tower cache_dirs: ============================================== Oct 16 12:33:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 12:33:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 12:33:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 12:33:00 Tower cache_dirs: max_depth=4 Oct 16 12:33:00 Tower cache_dirs: command=find -noleaf Oct 16 12:33:00 Tower cache_dirs: version=1.6.5 Oct 16 12:33:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 12:33:00 Tower cache_dirs: Videos Oct 16 12:33:00 Tower cache_dirs: ---------------------------------------------- Oct 16 12:33:00 Tower cache_dirs: cache_dirs process ID 17108 started, To terminate it, type: cache_dirs -q Quote Link to comment
Joe L. Posted October 17, 2013 Author Share Posted October 17, 2013 I have just started getting the same in my logs: Oct 15 22:25:04 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 15 22:26:00 Tower cache_dirs: ============================================== Oct 15 22:26:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 15 22:26:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 15 22:26:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 15 22:26:00 Tower cache_dirs: max_depth=4 Oct 15 22:26:00 Tower cache_dirs: command=find -noleaf Oct 15 22:26:00 Tower cache_dirs: version=1.6.5 Oct 15 22:26:00 Tower cache_dirs: ---------- caching directories --------------- Oct 15 22:26:00 Tower cache_dirs: Videos Oct 15 22:26:00 Tower cache_dirs: ---------------------------------------------- Oct 15 22:26:00 Tower cache_dirs: cache_dirs process ID 4369 started, To terminate it, type: cache_dirs -q Oct 15 22:27:48 Tower kernel: mdcmd (203): spindown 0 (Routine) Oct 15 22:27:48 Tower kernel: mdcmd (204): spindown 2 (Routine) Oct 15 23:19:49 Tower kernel: mdcmd (205): spindown 4 (Routine) Oct 15 23:20:00 Tower kernel: mdcmd (206): spindown 1 (Routine) Oct 15 23:20:00 Tower kernel: mdcmd (207): spindown 2 (Routine) Oct 15 23:20:00 Tower kernel: mdcmd (208): spindown 3 (Routine) Oct 15 23:20:01 Tower kernel: mdcmd (209): spindown 5 (Routine) Oct 15 23:20:01 Tower kernel: mdcmd (210): spindown 6 (Routine) Oct 15 23:20:51 Tower kernel: mdcmd (211): spindown 7 (Routine) Oct 15 23:50:02 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 15 23:51:00 Tower cache_dirs: ============================================== Oct 15 23:51:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 15 23:51:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 15 23:51:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 15 23:51:00 Tower cache_dirs: max_depth=4 Oct 15 23:51:00 Tower cache_dirs: command=find -noleaf Oct 15 23:51:00 Tower cache_dirs: version=1.6.5 Oct 15 23:51:00 Tower cache_dirs: ---------- caching directories --------------- Oct 15 23:51:00 Tower cache_dirs: Videos Oct 15 23:51:00 Tower cache_dirs: ---------------------------------------------- Oct 15 23:51:00 Tower cache_dirs: cache_dirs process ID 30794 started, To terminate it, type: cache_dirs -q Oct 16 01:14:29 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 01:15:01 Tower cache_dirs: ============================================== Oct 16 01:15:01 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 01:15:01 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 01:15:01 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 01:15:01 Tower cache_dirs: max_depth=4 Oct 16 01:15:01 Tower cache_dirs: command=find -noleaf Oct 16 01:15:01 Tower cache_dirs: version=1.6.5 Oct 16 01:15:01 Tower cache_dirs: ---------- caching directories --------------- Oct 16 01:15:01 Tower cache_dirs: Videos Oct 16 01:15:01 Tower cache_dirs: ---------------------------------------------- Oct 16 01:15:01 Tower cache_dirs: cache_dirs process ID 24715 started, To terminate it, type: cache_dirs -q Oct 16 02:17:13 Tower kernel: mdcmd (212): spindown 0 (Routine) Oct 16 02:17:14 Tower kernel: mdcmd (213): spindown 1 (Routine) Oct 16 02:41:06 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 02:42:00 Tower cache_dirs: ============================================== Oct 16 02:42:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 02:42:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 02:42:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 02:42:00 Tower cache_dirs: max_depth=4 Oct 16 02:42:00 Tower cache_dirs: command=find -noleaf Oct 16 02:42:00 Tower cache_dirs: version=1.6.5 Oct 16 02:42:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 02:42:00 Tower cache_dirs: Videos Oct 16 02:42:00 Tower cache_dirs: ---------------------------------------------- Oct 16 02:42:00 Tower cache_dirs: cache_dirs process ID 18694 started, To terminate it, type: cache_dirs -q Oct 16 03:15:45 Tower kernel: mdcmd (214): spindown 0 (Routine) Oct 16 03:15:45 Tower kernel: mdcmd (215): spindown 1 (Routine) Oct 16 03:16:16 Tower kernel: mdcmd (216): spindown 2 (Routine) Oct 16 03:29:26 Tower kernel: mdcmd (217): spindown 3 (Routine) Oct 16 04:02:47 Tower kernel: mdcmd (218): spindown 3 (Routine) Oct 16 04:02:57 Tower kernel: mdcmd (219): spindown 4 (Routine) Oct 16 04:03:07 Tower kernel: mdcmd (220): spindown 5 (Routine) Oct 16 04:04:17 Tower kernel: mdcmd (221): spindown 7 (Routine) Oct 16 04:05:28 Tower kernel: mdcmd (222): spindown 2 (Routine) Oct 16 04:07:38 Tower kernel: mdcmd (223): spindown 1 (Routine) Oct 16 04:08:49 Tower kernel: mdcmd (224): spindown 6 (Routine) Oct 16 04:37:39 Tower kernel: mdcmd (225): spindown 1 (Routine) Oct 16 04:40:02 Tower su[13762]: Successful su for unraid-plex by root Oct 16 04:40:02 Tower su[13762]: + root:unraid-plex Oct 16 04:44:23 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 04:45:00 Tower cache_dirs: ============================================== Oct 16 04:45:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 04:45:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 04:45:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 04:45:00 Tower cache_dirs: max_depth=4 Oct 16 04:45:00 Tower cache_dirs: command=find -noleaf Oct 16 04:45:00 Tower cache_dirs: version=1.6.5 Oct 16 04:45:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 04:45:00 Tower cache_dirs: Videos Oct 16 04:45:00 Tower cache_dirs: ---------------------------------------------- Oct 16 04:45:00 Tower cache_dirs: cache_dirs process ID 14478 started, To terminate it, type: cache_dirs -q Oct 16 04:57:50 Tower kernel: mdcmd (226): spindown 3 (Routine) Oct 16 04:58:00 Tower kernel: mdcmd (227): spindown 5 (Routine) Oct 16 04:58:00 Tower kernel: mdcmd (228): spindown 6 (Routine) Oct 16 04:58:01 Tower kernel: mdcmd (229): spindown 7 (Routine) Oct 16 05:16:51 Tower kernel: mdcmd (230): spindown 1 (Routine) Oct 16 05:17:12 Tower kernel: mdcmd (231): spindown 4 (Routine) Oct 16 05:17:42 Tower kernel: mdcmd (232): spindown 6 (Routine) Oct 16 05:29:13 Tower kernel: mdcmd (233): spindown 2 (Routine) Oct 16 05:33:33 Tower kernel: mdcmd (234): spindown 3 (Routine) Oct 16 05:33:33 Tower kernel: mdcmd (235): spindown 5 (Routine) Oct 16 05:33:33 Tower kernel: mdcmd (236): spindown 7 (Routine) Oct 16 06:28:54 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 06:29:00 Tower cache_dirs: ============================================== Oct 16 06:29:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 06:29:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 06:29:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 06:29:00 Tower cache_dirs: max_depth=4 Oct 16 06:29:00 Tower cache_dirs: command=find -noleaf Oct 16 06:29:00 Tower cache_dirs: version=1.6.5 Oct 16 06:29:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 06:29:00 Tower cache_dirs: Videos Oct 16 06:29:00 Tower cache_dirs: ---------------------------------------------- Oct 16 06:29:00 Tower cache_dirs: cache_dirs process ID 8556 started, To terminate it, type: cache_dirs -q Oct 16 07:58:46 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 07:59:01 Tower cache_dirs: ============================================== Oct 16 07:59:01 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 07:59:01 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 07:59:01 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 07:59:01 Tower cache_dirs: max_depth=4 Oct 16 07:59:01 Tower cache_dirs: command=find -noleaf Oct 16 07:59:01 Tower cache_dirs: version=1.6.5 Oct 16 07:59:01 Tower cache_dirs: ---------- caching directories --------------- Oct 16 07:59:01 Tower cache_dirs: Videos Oct 16 07:59:01 Tower cache_dirs: ---------------------------------------------- Oct 16 07:59:01 Tower cache_dirs: cache_dirs process ID 2527 started, To terminate it, type: cache_dirs -q Oct 16 09:06:45 Tower kernel: mdcmd (237): spindown 3 (Routine) Oct 16 09:26:56 Tower kernel: mdcmd (238): spindown 2 (Routine) Oct 16 09:44:46 Tower kernel: mdcmd (239): spindown 2 (Routine) Oct 16 09:57:04 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 09:58:00 Tower cache_dirs: ============================================== Oct 16 09:58:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 09:58:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 09:58:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 09:58:00 Tower cache_dirs: max_depth=4 Oct 16 09:58:00 Tower cache_dirs: command=find -noleaf Oct 16 09:58:00 Tower cache_dirs: version=1.6.5 Oct 16 09:58:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 09:58:00 Tower cache_dirs: Videos Oct 16 09:58:00 Tower cache_dirs: ---------------------------------------------- Oct 16 09:58:00 Tower cache_dirs: cache_dirs process ID 29209 started, To terminate it, type: cache_dirs -q Oct 16 10:32:17 Tower kernel: mdcmd (240): spindown 2 (Routine) Oct 16 11:02:08 Tower kernel: mdcmd (241): spindown 2 (Routine) Oct 16 11:02:08 Tower kernel: mdcmd (242): spindown 7 (Routine) Oct 16 11:14:34 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 11:15:01 Tower cache_dirs: ============================================== Oct 16 11:15:01 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 11:15:01 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 11:15:01 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 11:15:01 Tower cache_dirs: max_depth=4 Oct 16 11:15:01 Tower cache_dirs: command=find -noleaf Oct 16 11:15:01 Tower cache_dirs: version=1.6.5 Oct 16 11:15:01 Tower cache_dirs: ---------- caching directories --------------- Oct 16 11:15:01 Tower cache_dirs: Videos Oct 16 11:15:01 Tower cache_dirs: ---------------------------------------------- Oct 16 11:15:01 Tower cache_dirs: cache_dirs process ID 23174 started, To terminate it, type: cache_dirs -q Oct 16 12:32:57 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 12:33:00 Tower cache_dirs: ============================================== Oct 16 12:33:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 12:33:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 12:33:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 12:33:00 Tower cache_dirs: max_depth=4 Oct 16 12:33:00 Tower cache_dirs: command=find -noleaf Oct 16 12:33:00 Tower cache_dirs: version=1.6.5 Oct 16 12:33:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 12:33:00 Tower cache_dirs: Videos Oct 16 12:33:00 Tower cache_dirs: ---------------------------------------------- Oct 16 12:33:00 Tower cache_dirs: cache_dirs process ID 17108 started, To terminate it, type: cache_dirs -q The cache_dirs program will re-schedule itself when it finds no mounted disks. (Or thinks there are no mounted disks) It uses this command: find /mnt/disk[1-9]* -type d -maxdepth 0 -print If the number of lines returned is 0 (regardless of the reason the "find" failed) then it simply re-schedules itself for 1 minute later. It should return one line per disk. You could be out of memory.... Try the "find" command on your own when this is occurring... Quote Link to comment
darkside40 Posted November 6, 2013 Share Posted November 6, 2013 Hi Joe L., after going away form Simple Features i wanted to use your cache_dir script the old fashined way on my unRaid Server (via the Go File). I wanted to test it before so i downloaded the script and try to start it but it throwed this failure: root@HTMS:/boot/custom/bin# ./cache_dirs -m 5 -M 10 -i "Movies" ./cache_dirs: xrealloc: subst.c:658: cannot allocate 177792 bytes (737280 bytes allocated) I checked my free memory and could not find anything wrong because there should be more than 3GB still be free (4GB installed in total) root@HTMS:/boot/custom/bin# free -l total used free shared buffers cached Mem: 4056892 351660 3705232 0 58964 213848 Low: 865252 120872 744380 High: 3191640 230788 2960852 -/+ buffers/cache: 78848 3978044 Swap: 0 0 0 Any idea? When i used Cache dirs under Simplefeatures it worked without any problems, but Simple Features was bit buggy the so i had to delete it. Quote Link to comment
zoggy Posted November 6, 2013 Share Posted November 6, 2013 So for lack of a more technical approach I am trying the tidy up route. This command added to bashrc alias duf='du -a | cut -d/ -f2 | sort | uniq -c | sort -nr' allows me to count files in dirs. Have to say I was surprised by some of the numbers hehe.. just for giggles i ran that command on /mnt/user/ 161915 Music 96022 Personal 10391 TV 7107 Movies 2017 Media Quote Link to comment
Joe L. Posted November 6, 2013 Author Share Posted November 6, 2013 Hi Joe L., after going away form Simple Features i wanted to use your cache_dir script the old fashined way on my unRaid Server (via the Go File). I wanted to test it before so i downloaded the script and try to start it but it throwed this failure: root@HTMS:/boot/custom/bin# ./cache_dirs -m 5 -M 10 -i "Movies" ./cache_dirs: xrealloc: subst.c:658: cannot allocate 177792 bytes (737280 bytes allocated) I checked my free memory and could not find anything wrong because there should be more than 3GB still be free (4GB installed in total) root@HTMS:/boot/custom/bin# free -l total used free shared buffers cached Mem: 4056892 351660 3705232 0 58964 213848 Low: 865252 120872 744380 High: 3191640 230788 2960852 -/+ buffers/cache: 78848 3978044 Swap: 0 0 0 Any idea? When i used Cache dirs under Simplefeatures it worked without any problems, but Simple Features was bit buggy the so i had to delete it. The "find" command was apparently trying to allocate a contiguous chunk of memory of that size, which you apparently did not have. Your memory, although free, was fragmented. Quote Link to comment
MartinQ Posted November 7, 2013 Share Posted November 7, 2013 The "find" command was apparently trying to allocate a contiguous chunk of memory of that size, which you apparently did not have. Your memory, although free, was fragmented. So what's the corrective action? Reboot the server? . Quote Link to comment
NAS Posted November 7, 2013 Share Posted November 7, 2013 So for lack of a more technical approach I am trying the tidy up route. This command added to bashrc alias duf='du -a | cut -d/ -f2 | sort | uniq -c | sort -nr' allows me to count files in dirs. Have to say I was surprised by some of the numbers hehe.. just for giggles i ran that command on /mnt/user/ 161915 Music 96022 Personal 10391 TV 7107 Movies 2017 Media What i fond was random stuff that had been dumped that came from windows had zillions of small files. Added up all thee backups and caches had hundreds of thousands of files Quote Link to comment
darkside40 Posted November 7, 2013 Share Posted November 7, 2013 Hi Joe L., after going away form Simple Features i wanted to use your cache_dir script the old fashined way on my unRaid Server (via the Go File). I wanted to test it before so i downloaded the script and try to start it but it throwed this failure: root@HTMS:/boot/custom/bin# ./cache_dirs -m 5 -M 10 -i "Movies" ./cache_dirs: xrealloc: subst.c:658: cannot allocate 177792 bytes (737280 bytes allocated) I checked my free memory and could not find anything wrong because there should be more than 3GB still be free (4GB installed in total) root@HTMS:/boot/custom/bin# free -l total used free shared buffers cached Mem: 4056892 351660 3705232 0 58964 213848 Low: 865252 120872 744380 High: 3191640 230788 2960852 -/+ buffers/cache: 78848 3978044 Swap: 0 0 0 Any idea? When i used Cache dirs under Simplefeatures it worked without any problems, but Simple Features was bit buggy the so i had to delete it. The "find" command was apparently trying to allocate a contiguous chunk of memory of that size, which you apparently did not have. Your memory, although free, was fragmented. Thats nearly impossible because i tried this directly after i rebooted the server. How can the memory be that fragmented after it. Quote Link to comment
Joe L. Posted November 8, 2013 Author Share Posted November 8, 2013 The "find" command was apparently trying to allocate a contiguous chunk of memory of that size, which you apparently did not have. Your memory, although free, was fragmented. So what's the corrective action? Reboot the server? . or add swap space, or free memory (kill memory hogs) Quote Link to comment
darkside40 Posted November 9, 2013 Share Posted November 9, 2013 I have no memory hungry things running. Only this which i have apart from stock unraid is dnsmasq and a S3 Sleep Script running. I have rebooted the server several time, clear the caches with an "echo 3 > /proc/sys/vm/drop_caches", i even switched the Ram from 1x 4GB Module to my older 2x 2GB Modules to see if the Ram is damaged. Nothing helped. Cache_dirs can simply not allocate that memory and i dont know why. Silly thing is, it works when i used it from inside Simplefeatures on the hardware in the sig. Now i use a Intel Haswell system (have to update the sig) and the new Webgui (already tried it without the new gui) and it does not work. Quote Link to comment
darkside40 Posted November 14, 2013 Share Posted November 14, 2013 Okay now i simply startet cache_dirs using this command "./cache_dirs -m 5 -M 10 -w" Now it seems to be running. Is there anyway to determinate if cache_dirs has successfully put the directory entries into memory? Quote Link to comment
Joe L. Posted November 16, 2013 Author Share Posted November 16, 2013 Okay now i simply startet cache_dirs using this command "./cache_dirs -m 5 -M 10 -w" Now it seems to be running. Is there anyway to determinate if cache_dirs has successfully put the directory entries into memory? You are not understanding how it works... cache_dirs does nothing except perform the equivalent of doing a "search" on your directories for all the files and throwing away the resulting file list to /dev/null. The very act of traversing the file-system tree puts those disk blocks into the disk buffer cache. The only thing cache_dirs does is repeat the search every few seconds so the most frequently accessed disk blocks do not "age" out of the disk buffer cache. To see what it does, kill it and re-run it in the foreground instead of in the background. ./cache_dirs -q ./cache_dirs -F -v The -m and -M are automatically set by cache_dirs. There is no need to use them unless you find the default is not working for you. The -w option is needed only if you invoke cache_dirs while the array is off-line. It will then have cache_dirs wait for the array to be on-line before starting a scan of the directory tree. Therefore, if the array is started, it is not needed either. -F = foreground -v = more verbose output. Quote Link to comment
blingbling1384 Posted November 26, 2013 Share Posted November 26, 2013 My understanding was that cache_dirs was supposed to cache the directory information so that the disks did not need to spin up while simply traversing the directory structure. Is this not the case? I can see in the syslog that cache_dirs runs without errors upon startup, but the disks still spin up when I'm browsing through directories (not accessing files). Quote Link to comment
JonathanM Posted November 26, 2013 Share Posted November 26, 2013 the disks still spin up when I'm browsing through directories (not accessing files). Many disk browsers access the files to determine file type and display thumbnails. Quote Link to comment
elmetal Posted December 22, 2013 Share Posted December 22, 2013 my cache_dirs will randomly stop running (I don't know if it has to do with the fact that I am doing preclears) is there a quick script anyone has that I can add to my crontab to make sure it's always running? (say run the script every 30 mins) I can make something right quick but if someone already has that'd be sweet thanks guys Quote Link to comment
Superorb Posted December 27, 2013 Share Posted December 27, 2013 Can this be installed as a plugin or only as a GO-launched script? Quote Link to comment
DaleWilliams Posted December 27, 2013 Share Posted December 27, 2013 Can this be installed as a plugin or only as a GO-launched script? Check out Dynamix, Bonienl's new web gui. Add-ins include cache-dirs http://lime-technology.com/forum/index.php?topic=30939.0 Quote Link to comment
Superorb Posted December 27, 2013 Share Posted December 27, 2013 Check out Dynamix, Bonienl's new web gui. Add-ins include cache-dirs http://lime-technology.com/forum/index.php?topic=30939.0 I already use unMENU and its package manager, will they work well together? Quote Link to comment
DaleWilliams Posted December 28, 2013 Share Posted December 28, 2013 I already use unMENU and its package manager, will they work well together? I don't know, sorry. Dynamix seems to be a 'branch' of the old SimpleFeatures that's fixed to work with 5.0...I can't speak to how it plays with unMENU. The optional add-in plugins include cache-dir, SMART, email notifications, etc. Quote Link to comment
langrock Posted January 6, 2014 Share Posted January 6, 2014 Hi, I noticed that the cache_dirs process will ignore the folder(s) specified in the 'Excluded folders (separated by comma):' section of SimpleFeatures GUI of unRAID 5.0.4. For example, I have a 'Plex" share which lives only on the cache drive. I had noticed that whenever cache_dirs was looking into this directory the CPU usage went up by a lot, >100% on a dual-core AMD machine. I was hoping that instructing cache_dirs to ignore this directory would work, but alas, I still see the process looking into this directory by issuing ps fo pid,cmd -U root on the command line at the right moment. The processes in question are /bin/bash /usr/local/sbin/cache_dirs -w -B -m 10 -M 600 -d 9999 -e 'Plex' 27607 \_ /bin/bash /usr/local/sbin/cache_dirs -w -B -m 10 -M 600 -d 9999 -e 'Plex' 27636 \_ find /mnt/cache/Plex -noleaf which does have 'Plex' as argument for the -e option. I also set the scan interval to 10 seconds since I didn't understand why this process would need to be run every second. Maybe I don't understand how to properly use the exclude function. I would appreciate helpful comments. The share I'd like to exclude is '/mnt/cache/Plex'. I had also tried to enter the full path name in 'Exclude folders' section with no success. Thanks in advance, Carsten Quote Link to comment
jeff.lebowski Posted January 6, 2014 Share Posted January 6, 2014 the disks still spin up when I'm browsing through directories (not accessing files). Many disk browsers access the files to determine file type and display thumbnails. Windows Explorer, for example. One of many reasons I switched from WE to Total Commander. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.