Hello, 

My cache SSD has 232/240GB used and is reporting full in the system logs, and the mover is not moving anything off the disk. I have two storage disks both set to "Prefer" cache, though one I changed from Yes to Prefer after the disk filled up. Manually starting the mover yields  many of these errors: 

 

Dec 8 12:22:47 Knox move: move: file /mnt/disk1/documents/.../06 Pinocchio.m4a 
Dec 8 12:22:47 Knox shfs: share cache full

 

My dockers are turned off. I ran a balance but that didn't do anything. Appreciate any advice. Thanks!

 

 

Edited December 8, 20214 yr by digitoxin

Haven't looked at diagnostics yet, but since I already posted about a lot of this in another thread recently I will link to it. Long story short, "prefer" doesn't mean what you think it does, and there are a lot of other things to consider.

 

 

 

In addition to what I already discussed in that other thread, you have 2 user shares that are anonymized in diagnostics like this:

d-------s

d-------s (1)

This often means that you have 2 shares with the same name except for upper/lower case. Could also just mean that they have the same number of letters with the same beginning and ending, can't tell because of anonymizing. If you do have 2 shares with the same name, you need to fix that.

 

After you get your shares configured correctly and moved where they belong you should go to Scheduler settings and turn off mover logging unless you are trying to diagnose mover problems. Those aren't anonymized and can take a lot of syslog space.

 

 

d-------s = documents

d-------s (1) =  downloads

 

Thanks!

 

I will also look at the other thread

@trurl Thanks! I definitely had the meaning of Prefer backwards (i.e. I thought it would write directly to the array if the cache is full -- not the case!). I changed my shares to Yes and the cache is now emptying out. 

3 minutes ago, digitoxin said:

I thought it would write directly to the array if the cache is full

It will overflow to the array if writing new files and you have correctly defined "full" with the Minimum Free settings. But note that "prefer" also means "move TO cache".

  

3 hours ago, trurl said:

"Prefer" means write new files to cache if there is room, and keep them on cache. If there isn't room, write them to the array (overflow) instead, and move from array to cache according to the mover settings if room has become available. This setting is for files you intend to stay on cache.

 

3 hours ago, trurl said:

Each user share has a Minimum Free setting. Unraid has no way to know how large a file will become when it chooses a disk for it. If a disk has more than Minimum Free, the disk can be chosen and if the file won't fit, the write fails. Each pool (cache) also has a Minimum Free setting. You should set Minimum Free to larger than the largest file you expect to write to the share or pool.