Hello all,

 

So, I built an unraid server in 2011 using 4.7. I didn't want to spin up the drives all the time, so I got the cache dirs script and ran it. I then put a utility on my windows PC called Index Your Files which does exactly what it sounds like, it scans the directories every so often and builds a search index. As I recall Windows Search would wake the drives up and IYF did not spin up anything.  So, that ran pretty well until now.

 

Last night I upgraded to 5x and then the newest version of 6x. I got unmenu installed, and installed all my normal packages, the email thing, the UPS thing, all working great. I'm having a problem with indexing the server, though. When I manually index, or just let it automatically index, IYF finds nothing at all; as if there were no files on the server. The data actually IS on the server, and it's all great, and I've made no changes to IYF (which actually has almost no settings anyway, it's super simple) so I probably misconfigured cache_dirs somehow.

 

Here is my current syslog entry for cache dirs:

 

Nov  7 05:40:00 Shiva cache_dirs: ==============================================

Nov  7 05:40:00 Shiva cache_dirs: command-args=-w -m 1 -M 10 -d 9999 -p 10 -U 50000 -B -a -noleaf

Nov  7 05:40:00 Shiva cache_dirs: vfs_cache_pressure=10

Nov  7 05:40:00 Shiva cache_dirs: max_seconds=10, min_seconds=1

Nov  7 05:40:00 Shiva cache_dirs: max_depth=9999

Nov  7 05:40:00 Shiva cache_dirs: command=find -noleaf

Nov  7 05:40:00 Shiva cache_dirs: version=1.6.9

Nov  7 05:40:00 Shiva cache_dirs: ---------- caching directories ---------------

Nov  7 05:40:00 Shiva cache_dirs: Shared

Nov  7 05:40:00 Shiva cache_dirs: ----------------------------------------------

Nov  7 05:40:00 Shiva cache_dirs: cache_dirs process ID 3116 started, To terminate it, type: cache_dirs -q

 

So, I don't really know what those commands mean, but my guess is one of them is misconfigured.

 

Here is what the cache_dirs looked like on 4.7:

 

Oct 12 18:20:12 Shiva cache_dirs: ==============================================

Oct 12 18:20:12 Shiva cache_dirs: command-args=-w

Oct 12 18:20:12 Shiva cache_dirs: vfs_cache_pressure=10

Oct 12 18:20:12 Shiva cache_dirs: max_seconds=10, min_seconds=1

Oct 12 18:20:12 Shiva cache_dirs: max_depth=9999

Oct 12 18:20:12 Shiva cache_dirs: command=find -noleaf

Oct 12 18:20:12 Shiva cache_dirs: version=1.6.5

Oct 12 18:20:12 Shiva cache_dirs: ---------- caching directories ---------------

Oct 12 18:20:12 Shiva cache_dirs: Shared

Oct 12 18:20:12 Shiva cache_dirs: ----------------------------------------------

Oct 12 18:20:12 Shiva cache_dirs: cache_dirs process ID 4383 started, To terminate it, type: cache_dirs -q

 

So what do I need to change? And how?

 

Thank you very much.

 

Did you export the share?

Has the IP of the server changed?

Can you browse the share when you go to the IP address?

Did you use the latest version of cache_dirs?

Does everything work when cache_dirs is not running?

Why are you assuming cache_dirs has something to do with running a PC application that to retrieve the directory listing?

 

Not being sarcastic, but you made two major upgrades to your system and are assuming an issue you are having is related to a specific utility.  Why are you making this assumption?  There are several things that could be misconfigured.

Did you export the share?

 

This is what it was. Thank you. I could browse to it on my PC via explorer, and mapped it as a drive, so I didn't check that the share was actually being exported - I assumed if it wasn't I wouldn't see it at all.