[cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up]

Thanks Joe, you're the best!

 

 

[cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up]

Hi Joe,

 

I could greatly use some help with cache dirs. I recently upgraded my mobo to a biostar 760+ and upgraded to unraid 4.54.

 

I call cache_dirs in my go script using: /boot/cache_dirs -d 5 -w -e "VMC"

 

Everything was working for a few weeks but now twice in the past 3 days I got some strange error that hard froze unraid (can't telnet to it, can't refresh the unmenu/web, when I manually hook up a monitor to it no commands are acknolwedged, can't see it on the network etc). It doesn't freeze after a reboot or anything but some random time afterwards (hours/days).

 

This is what the last few syslog lines read from Unmenu:

Jun 15 05:51:33 Tower kernel: [] ? sys_read+0x3b/0x60

Jun 15 05:51:33 Tower kernel: [] ? syscall_call+0x7/0xb

Jun 15 05:51:33 Tower kernel: Code: 55 f0 e8 8a 82 d5 c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 a0 3d 3e f8 c1 e9 02 89 38 a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89

Jun 15 05:51:33 Tower kernel: EIP: [] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c238bef4

Jun 15 05:51:33 Tower kernel: CR2: 00000000f83e8000

Jun 15 05:51:33 Tower kernel: ---[ end trace 6baff4c42c121ab7 ]--

 

I see some different error messages when I go to the unraid box itself, a lot of stuff but this is the part that makes me think it is something cache_dirs related:

 

/boot/cache_dirs/: Line 479: 30756 killed

$command "$i"/$share_dir" $depth > /dev/null 2>&1

 

I know my cache_dirs call is slightly modified from before (I didn't use to exclude the "VMC" folder), so I'll try just calling it with -w and see what happens.

Any help is greatly appreciated!