Here is my situation.  I preveously had installed all my applications like plexmedia server,  sabnzbd, etc onto the array and it was working fine but I always read you are to put them on a cache drive.  So I bought a 128gb PCI-E-SSD and then moved my apps directory from the previous location of /mnt/user/apps to /mnt/cache/apps.

 

I added the drive as a cache drive as you can see:

 

 

In the share settings I have it set to cache only.

 

 

But as you can see I did not specify anything like include or external disks.

 

Also I have never seen a "mover" script menu like some of the screenshots I found here when looking.

 

My issue is this -  Every morning all of my applications bomb out with errors.  It drove me crazy..  Then I realized it must have been the mover moving them over from the cache drive so then the apps would bomb out.

 

Whats the best practice for what I am trying to do?  I only want to run apps from this almost like its a drive outside of the array but from the looks of it,  it is very much part of the array as any file I make in that cache directory a share is created.

 

Should I just suck it up and name it .apps folder?  Or should I take it out of the array and mount it separate?  Or should I just put my apps back into the main share?

 

I would like to do this correctly.  I think I am using the cache drive for something its not intended?

The cache should function exactly how you want it to!

 

However one thing that will mess it up is you have an apps folder at the top level on any of the array drives.  In that case the apps share does not seem to get treated as if were cache only (I suspect this is a bug) despite the setting on the share.  You need to look through each of the individual disk shares to see if there is an app folder present, and if so removing it should stop files being moved to the array.