I had the same thing happen last night. I updated to the new version for unraid 7 a week or so ago. Last night my cache_work <- array share put all the files in the array.

I have the settings 
Only move if above this threshold of used Primary (cache) space:
and
Free down/prime up to this level of used Primary (cache) space:
both set to 0% (I assume the default when I did the update).

I just manually kicked off the mover via the Main page, and the files moved back.

47 minutes ago, robsin said:

and the files moved back

By unraid mover or plugin? 

4 hours ago, alturismo said:

with the plugin rules AND the prefer rule ... it seems a hit or miss if that works or not

I'm little confused how plugin should work for prefer cache. Need more checking the code. In last version fixed issue when cache prefer or unnanttend and rebalanced was used for find /mnt/*/sharename not worked becose of * symbol. Now it's finding all /mnt/*/sharename but seems broked another thing... 

50 minutes ago, Masterwishx said:

By unraid mover or plugin? 

Sorry by unraid mover via the Main page button. I didn't realize that it could be separate processes, makes sense thinking about it, sorry.

So CA Mover tunning moved them all last night, clicking Main/Move (button) moved them back.

1 hour ago, Masterwishx said:

I'm little confused how plugin should work for prefer cache. Need more checking the code. In last version fixed issue when cache prefer or unnanttend and rebalanced was used for find /mnt/*/sharename not worked becose of * symbol. Now it's finding all /mnt/*/sharename but seems broked another thing... 

Normally it should keep all files on the cache when possible \ until full and overflow only to the array if necessary. If files are on the array for any reason and space is free on the cache, it should move them to the cache. Now there is an issue where files are moved from the cache to the array.

To be honest I've since removed the plugin; I changed it to (I think) your version, because I'd seen the 'prime/drain to x%' feature which was exactly what I was looking for for quite some time, but I was using 2025.03.01.

9 hours ago, Masterwishx said:

Any prs are welcome, I think it should write to file maybe and then add it to filter list? @foux if it long ignore list. 

I have pushed up a PR.

 I havnt had chance to look at the other issues for now.

9 hours ago, Masterwishx said:

I'm little confused how plugin should work for prefer cache. Need more checking the code. In last version fixed issue when cache prefer or unnanttend and rebalanced was used for find /mnt/*/sharename not worked becose of * symbol. Now it's finding all /mnt/*/sharename but seems broked another thing... 

personal suggestion, skip them as its a weird setup anyhow in combination with this plugin.

 

with mover tuning installed, intention should be to keep cache > array Shares also "longer" on cache, with the treeholds to free you should always be fine without touching cache prefer Shares anyway ... IF mover scheduled often enough to take care on the regular cache > array Shares ...

 

cause nevertheless, once you touch the cache prefer Shares also, it will always be a ping pong game ...

 

so may either add another treehold for those Shares when moving and priority (those Shares AFTER regular cache > array)

 

1/ regular mover starts on sample 80 % (starting with cache > array Shares)

2/ regular mover stops when below 50 % (all regular Shares)

 

even when then we are now on 55 % ... (as regular cache > array are done) what todo now with the cache prefer Shares ... move them also (5 %) or lets say take the 80 % treehold as trigger therefore only AFTER cache > array Share moves are done or ...

 

in sum, its a pain setup to use those Shares anyhow together with something like mover tuning, recommended should be (personal opinion), keep it as

 

cache > array Shares (follow the plugin rules)

cache only Shares (not touched by this plugin, make your Backups !!!)

array only Shares (not touched by this plugin, also consider your Backups !!!)

 

and there should be no conflicts ... and no issues which Shares are touched when ...

 

that crappy cache prefer is most likely used in /appdata /system /domains ... Shares, which mostly cant be really handled anyhow as "files in use" and rather breaks stuff instead be a benefit ... also the ping pong Game ... move files to array, next time, move them back to cache when there is space left ... also alot setup /mnt/cache/... to bypass FUSE in Services but using cache prefer Share Layouts, which will also break stuff once stuff is moved away from cache and so on ...

28 minutes ago, alturismo said:

in /appdata /system /domains ... Shares, which mostly cant be really handled anyhow

Thanks, I'm personally using cache only (exclusive) for thouse... 

I need check what's going on... 

1 minute ago, Masterwishx said:

Thanks, I'm personally using cache only (exclusive) for thouse... 

Same here 😉

47 minutes ago, alturismo said:

even when then we are now on 55 % ... (as regular cache > array are done) what todo now with the cache prefer Shares ... move them also (5 %) or lets say take the 80 % treehold as trigger therefore only AFTER cache > array Share moves are done or ...

I will try to check it, but I think when checked unraid mover code it's only move from array to cache when prefer

Not shure if was % check in Mover code... 

OK, I found where issue with cache prefer. So I can disable to move from primary cache when prefer or set like 95% for threshold 0% freeing in code... 

For now, after will think about more... 

Edited March 4, 20251 yr by Masterwishx

It will skip moving for cache prefer on primary, if cache 100% full set freeing to 98%

19 hours ago, JonasH said:

Now there is an issue where files are moved from the cache to the array.

Updated version with the fix

7 hours ago, Masterwishx said:

Updated version with the fix

Thank you! It is working now, but this maybe needs a more elegant solution.

Does anyone know what the second part of this image means?

 

Free down/prime up to this level of used Primary (cache) space:

 

Goal:  To activate the mover when over 75% of cache drive is used

 

 

Am I doing this right?

 

Thank you!

36 minutes ago, taflix said:

Am I doing this right?

 

exactly, once your cache is filled > 75 % AND mover is triggered (scheduled run) then it will start moving files down to ~ < 15 %

5 hours ago, JonasH said:

more elegant solution.

Yep

10 hours ago, alturismo said:

exactly, once your cache is filled > 75 % AND mover is triggered (scheduled run) then it will start moving files down to ~ < 15 %

Thanks, your explanation is much easier to understand.

 

The "?" should be updated to something like:

Run the mover until storage used on the cache pool reaches this amount.  Example, 0% means move everything off the cache pool.

 

Just wondering if the recent update has introduced a bug?  Setting is pretty vanilla (per screenie below), but it looks to be ignoring and not trying to move until it hits 99%...

 

Primary storage: cache_ssd - size: 932GiB - used:  83 % (772GiB)
Secondary storage: user0
Share Information: Name: zFileSwap - Path: /mnt/cache_ssd/zFileSwap
Moving threshold: 99% (923GiB) ; Freeing threshold: 0% (0B)
Mover action: cache_ssd->user0 (cache:yes). Pool is below moving threshold percentage:  83% < 99%.
=> Skipping

 

31 minutes ago, bbbilly05 said:

Just wondering if the recent update has introduced a bug

It was fix for cache prefer in your case it's cache yes, not sure how it's possible, will check it

36 minutes ago, bbbilly05 said:

Setting is pretty vanilla (per screenie below), but it looks to be ignoring and not trying to move until it hits 99%...

Did you changed share to prefer when mover run? 

16 hours ago, JonasH said:

more elegant solution.

How exactly you using cache prefer? Maybe separate thresholds and age for cache prefer ? 

1 hour ago, Masterwishx said:

Did you changed share to prefer when mover run? 

Hi Masterwishx,

 

Confirming that share is cache > array when mover runs.  It happens across all shares, not just that one - but I'd grabbed it as an example.

 

B.

 

3 hours ago, taflix said:

The "?" should be updated to something like

Done