I am having odd behavior with my cache drive that manifesting itself with files "disappearing" and SABnzbd not being able to write its .ini.bak file.  It seems all this happened after a reboot after I expanded the array.

 

Using Finder, and looking at the cache share (or via telnet /mnt/cache/)

 

/cache/

  _apps/

    couchpotato_v2/

    sabnzbd/

    sickbeard/

 

  _downloads

    admin/

    Downloads/

    logs

 

Now using telnet and looking at /mnt/user/

 

  _apps/

    couchpotato_v2/

    sabnzbd/

    sickbeard/

 

  _downloads

    admin/

    Downloads/

    logs

    sabnzbd.ini

    sabnzbd.ini.bak

 

Note that the sabnzbd files are under the /mnt/user/.  If I dig further into /mnt/user/_downloads/ I find things in /Downloads/ that had disappeared.

 

I have the exclude directories beginning with "_" from being moved from the cache drive via unMenu installed and configured for reboot.  It would appear the files got moved into the protected array.

 

I am not sure other that brute force how to but the files back, or have then stay put.

 

Also note the _apps and _downloads show up as user shares via SMB - I did not set them this way.

 

------

7/22  update:

 

Seems mover is moving the "_" directories even though I have invoked the pkg to exclude in Unmenu.  Syslog attached - any ideas?

syslog-2012-07-24.txt.zip

Seems mover is moving the "_" directories even though I have invoked the pkg to exclude in Unmenu.  Syslog attached - any ideas?

The "mover" script changed when lime-tech added the ability to mark specific shares as "cache only" as part of the changes in the 5.0beta series.

 

The unMENU package has no effect on the new mover script. (it does no harm, but makes no changes either, since it no longer has the same regular expression to find and edit)

 

The solution... mark the share as "cache only" in the unRAID interface.  You'll also probably need to manually delete the equivalent directories on the data disks, since if present, the share is considered one where moving files from the cache drive is allowed.  (marking it as share only prevents the directories from being created)

Joe L,

 

Thanks for the clarity. 

 

Now when you say "mark the share as "cache only"', I am not quite clear where to do this in the unRAID interface.  How to set it up is not well documented.

 

From the wiki:

When the cache disk is not enabled, it will may still be exported and accessed like any other disk share, but any top-level directories will not be folded into user shares. In addition, the mover will be disabled.

 

Why would one want to disable the cache disk?

Though each share as a separate control for enabling use of the cache disk, this is a handy way to disable it's use for all shares temporarily.

You may want to disable the mover temporarily.

 

From the above I gather:

 

Under the Setting Tab/Share Settings there is a Cache Settings with a Use toggle and a size.  I should turn Cache to OFF, but set a size.

 

Under Shares Tab and going into a user share, there is a toggle box for "Use Cache Disk". I assume this sets the use of the cache for the share even when Cache is off above.  Only the user share data will be moved into the array from the cache drive.

 

Please confirm if I have it correct

 

Thanks

 

 

 

 

 

under the shares settings section the drop down should have an option to make that user share as "Cache Only"

SOLVED:  Set up new share for apps and downloads, included only cache drive and set USE CACHE DISK:  ONLY