Masterwishx

I meaned only for fill cache<array Not moving back to array as we only want move to cache for cache prefer

Thanks a lot again. Well it's really headache, in short I will leave only cache<array for cache prefer. I just buyed a bigger size ssd for appdata etc and made cache only. So next question if we need move threshold option for like move from array to cache until 95% or maybe fixed 95% or maybe: fixed cache size - minimum space=move threshold?

Yep I also use cache only for appdata etc.. But seems users use cache prefer for some media...

Yep. This by unraid mover design only move to cache from array. Then unraid write to array and when cache is free again mover should move to cache So I think the idea of author of plugin was automatically free cache by moving old files to array but seems it was not working good at least by autoage. Also not sure all users will want to move old files back to array? Also this move to array option seems like cache:yes and confusing but can be easily implemented as it's already in code. So move back to array?

So after discussing in github it seems cache:prefer should only move to cache from array. And not move back at all?

@alturismo If you can check our discussion will be cool. https://github.com/masterwishx/ca.mover.tuning/issues/25

This will work same as cache:yes to move data from cache to array

i added thresholds for cache prefer it good and understood enough ?

Yep you are right, but seems people want use cache prefer. So I'm trying to add thresholds for this when to move back to array like move when primary cache is after 95% freeing upto 90%. But then it's same setting like cache yes thresholds but for cache prefer. I can make both fixed and then It's can be done in share override setting or I can make global setting also. Or to make fixed 95% when to move that can be overrides in share setting and global only freeing like 90%. What do you think? Ohh seems it's find + sort and Inode. Thanks need to check not sure it's working right...

If you can find this instruction will be cool becose I'm trying to understand how the previous maintainer coded this to work..

It was really worked for you? I my testing for cache prefer it's moving to files to array and back to cache based on auto age, can't find on what really age it's based, so files going to cache and back to array every move when befor freeing threshold? Like @alturismo said it's not really how cache prefer should work. It need move all files to cache until full. So will try to add thresholds for cache prefer in this way

Try to remove config file and set all again

This was temporary fix for cache prefer, working now on include sepate thresholds for cache prefer

Do you have set test mode to No?

So I can add separate thresholds for cache prefer for not change code logic Becouse not shure why move data when below freeing threshold for prefer. So users can set 95 to 0% and it will skip moving data like I made fix in last version...

@alturismo I think we need add separate thresholds and age? for cache prefer Not sure why in plugin we have : elif [ "$POOLPCTUSED" -lt "$FREEINGPCTLIMIT" ]; then mvlogger "Mover action: $SECONDARYSTORAGENAME->$PRIMARYSTORAGENAME (cache:prefer). Pool is below priming threshold percentage: $POOLPCTUSED% < $FREEINGPCTLIMIT%." mvlogger "=> Will smart move newest files from $SECONDARYSTORAGENAME to $PRIMARYSTORAGENAME until threshold. Older files will be moved from $PRIMARYSTORAGENAME to $SECONDARYSTORAGENAME."

I can check it, please open issue on github

Thanks it is Is sometime plugin was working for cache prefer when low than freeing threshold it was moving data?

Do you want to move data in cache prefer befor 99%?

Maybe I will find more fine solution for this

This is not same it's fix for cache prefer for not to move data befor 99%

Please open issue in github include log and debug. Strange I can't really reproduce it, I have many cache yes shares, all ok. Seems no other people has it..

Done

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

Did you changed share to prefer when mover run?