Mover is not respecting the global moving/freeing threshold configuration

[geransmith]

Mar  5 11:31:55 falcon move: ----------------------------------------------------------------- Global settings ---------------------------------------------------------------
Mar  5 11:31:55 falcon move: Using global moving threshold: 80 %
Mar  5 11:31:55 falcon move: Using global freeing threshold: 40 %
Mar  5 11:31:55 falcon move: Age: Automatic (smart caching)
Mar  5 11:31:55 falcon move: Clean Folders: yes
Mar  5 11:31:55 falcon move: Test Mode: yes
Mar  5 11:31:55 falcon move: Notify: errorsOnly
Mar  5 11:31:55 falcon move: Debug Logging: yes
Mar  5 11:31:55 falcon move: Validate Filenames: yes
Mar  5 11:31:55 falcon move: ***************************************************************** FILTERING FILES ***************************************************************
Mar  5 11:31:55 falcon move: ------------------------------------------------------------ Processing [media] share -----------------------------------------------------------
Mar  5 11:31:55 falcon move: Primary storage: cache_download - size: 239GiB - used:  16 % (37GiB)
Mar  5 11:31:55 falcon move: Secondary storage: user0
Mar  5 11:31:55 falcon move: Share Information: Name: media - Path: /mnt/*/media
Mar  5 11:31:55 falcon move: Moving threshold: 99% (237GiB) ; Freeing threshold: 0% (0B)
Mar  5 11:31:55 falcon move: Mover action: user0->cache_download (cache:prefer). Pool is above freeing threshold percentage and below priming threshold percentage: 0% <  16% < 99%.
Mar  5 11:31:55 falcon move: => Skipping

My expectation would be that the "Media" share would be primed up to 40% since the primary storage is the cache.

[masterwishx]

As I posted in forum it's temporary fix for cache prefer not to move data befor 99%.
Becouse when people have threshold 0% and 0% it was moving data from cache prefer.

But cache prefer is to hold as much data on cache!

[masterwishx]

Maybe we need separate thresholds and age for cache prefer...

[geransmith]

Maybe we need separate thresholds and age for cache prefer...

This would be a really elegant solution to it!

[masterwishx]

Maybe we need separate thresholds and age for cache prefer...

This would be a really elegant solution to it!

is the cache prefer thresholds sometime worked for you ?

[Renegade605]

Maybe we need separate thresholds and age for cache prefer...

I would suggest that cache prefer moves should always run as long as there is space, and then free space with cache yes.

This is all a little messy with Unraid's new "any primary, any secondary, mover in either direction" design.

Instead of thinking of it like cache yes / prefer, it probably needs a rethinking of the purpose of Mover. When configuring a share, there is primary and secondary storage, and the mover action (source -> destination) can be primary -> secondary or secondary -> primary.

I propose that when moving files, thresholds should be checked for source only, never destination, instead of always for cache. You could have a separate threshold for each source. So threshold for Array could be 0%, and any moves from Array to Cache would always run. (Or, you could not have thresholds for Array at all.)

[geransmith]

is the cache prefer thresholds sometime worked for you ?

I don't think it is working for me. I honestly have had it on dry run mode for a bit since my cache isn't filling up.

My ultimate goal would be to have the mover move files if my cache is more than 80% full and go down to 40% full (which is what I have configured). I'd also want in all cases to have the cache prime to 40%.

I may be an outlier, but I just use cache to improve write speeds and keep my disks spun down. I assume recently written files would be the most accessed, so I want to keep those on the cache as long as possible.

[masterwishx]

Well I'm little confused about cache prefer, by current code without last fix for fixed thresholds for prefer.
Mover move when low than freeing for new old files to cache and array, I can't understand what exactly age it's using when age=-1 for default. But I will check more

[masterwishx]

primary -> secondary or secondary -> primary.

It's what is now in Unraid cache:yes cache:prefer

[masterwishx]

I propose that when moving files, thresholds should be checked for source only, never destination, instead of always for cache. You could have a separate threshold for each source. So threshold for Array could be 0%

So basically we need only freeing limit for cache prefer, when full how much space to free
Let's say up to 95% or so?

[Renegade605]

I propose that when moving files, thresholds should be checked for source only, never destination, instead of always for cache. You could have a separate threshold for each source. So threshold for Array could be 0%

So basically we need only freeing limit for cache prefer, when full how much space to free Let's say up to 95% or so?

Probably what you want is for Primary -> Secondary you have a moving and a freeing threshold like now so there's always space on primary.
For Secondary -> Primary always run regardless of free space. A hard limit of 95% full on primary is probably fine.

Either way, we probably don't care about how much free space is on Secondary.

[masterwishx]

Either way, we probably don't care about how much free space is on Secondary.

Yep I meaned only for primary

[masterwishx]

is it good ?

[masterwishx]

this will basically work as cache:yes