1 hour ago, ronia said:

age_mover to simulate as if the "move now"

You can see all parameters by "mover help".

So you can run "mover start" it will call age_mover start or mover.old start

whatever setting you have.

Similar like cron run it or mover button when pressed.

Also you can run age_mover or mover.old directly by start parameter.

2 hours ago, ronia said:

is I want to write a small script that essentially hits the "Move Now" button

Not sure what Javascript function runned when move now button pressed not founded in php.

IIRC when checked in htop there is no parametr (parent proccess) howere it should be (emhttp, shcmd) sended with mover.php when mover button pressed, so you can see in syslog when debug enabled (bash,crond or button pressed (if blank parametr ) in code.

Edited June 17, 20251 yr by Masterwishx

Plugin is not respecting threshold number.

I have it set to run every hour, but only move if cache is above 70%, and bring it down to 50%.

Yet, every hour is moves everything even when cache is sitting at 40%.

Edited June 17, 20251 yr by PSteger
clarity

10 hours ago, Masterwishx said:

Not sure what Javascript function runned when move now button pressed not founded in php.

IIRC when checked in htop there is no parametr (parent proccess) howere it should be (emhttp, shcmd) sended with mover.php when mover button pressed, so you can see in syslog when debug enabled (bash,crond or button pressed (if blank parametr ) in code.

Thanks @Masterwishx , it seems to have worked:

/usr/local/sbin/mover start |& logger -t move &

And from what I can tell, it seems to have followed all my mover rules as well which is good.

I'm going to try testing this a bit more and writing a user script for this, but this looks promising.

2 hours ago, PSteger said:

Yet, every hour is moves everything even when cache is sitting at 40%.

Post your config

1 hour ago, PSteger said:

First you need more gap between thresholds if have big files.

If you say it move after 40%, enable logs and debug wait when mover run then post debug.zip

As configured, shouldn't it not be attempting to move anything until it gets up to 70% full?

28 minutes ago, PSteger said:

As configured, shouldn't it not be attempting to move anything until it gets up to 70% full?

Yep after 70% move threshold

15 hours ago, Masterwishx said:

Yep after 70% move threshold

Debug.zip

Is this want you want? All the log files zipped up.

For now I've set "Synchronize Primary files to Secondary" since it doesn't seem to do anything anyway and it appears in the mover tuning log as a possible reason for my issue.

I thought that setting would make a copy my cache only files and put them on the array for parity, but maybe I was wrong.

Edited June 18, 20251 yr by PSteger
additional information

37 minutes ago, PSteger said:

Is this want you want? All the log files zipped up.

You can get debug.zip in help menu of plugin or in cli by "mover debug"

On 6/16/2025 at 7:47 PM, chowpay said:

So Reading this I expect that 517GiB was moved off my 2TB cache. Not the case I don't know what it moved but my cache level didn't change

You probably still have test mode enabled, turn it off.

13 hours ago, Masterwishx said:

You can get debug.zip in help menu of plugin or in cli by "mover debug"

debug.zip

3 hours ago, PSteger said:

debug.zip

from list file :

`cache|user0|Media|yes|1750238329|512104247296|11925590110|1|1|6322601|/mnt/cache/Media/TVShows/The Expanse (2015) {tvdb-280619}/Season 01/The Expanse (2015) - S01E06 - Rock Bottom [Bluray-1080p Remux Proper][DTS-HD MA 5.1][AVC]-NOGRP.mkv`

here cache :prefer is used and this threshold for it (fillupThreshold="0" ), if "0" it should not move i think at all.

here: 70% >= 70% so all fine here .

06:00:02.084 Primary storage: cache - size: 954GiB - used:  70 % (660GiB)
06:00:02.085 Secondary storage: user0
06:00:02.088 Share Information: Name: ImmichMedia - Path: /mnt/cache/ImmichMedia
06:00:02.090 Moving threshold: 70% (668GiB) ; Freeing threshold: 50% (477GiB)
06:00:02.091 Mover action: cache->user0 (cache:yes). Pool is above moving threshold percentage:   70% >= 70%.
06:00:02.092 => Will smart move old files from cache to user0. Nothing will be moved from user0 to cache
06:00:02.105 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-06-18T060001.list for ImmichMedia
06:00:02.109 ----------------------------------------------------------- Processing [MakeMKV] share ----------------------------------------------------------
06:00:02.122 Primary storage: cache - size: 954GiB - used:  70 % (660GiB)
06:00:02.123 Secondary storage: user0
06:00:02.127 /mnt/cache/MakeMKV does not exist. Is the share still used? Consider removing /boot/config/shares/MakeMKV.cfg if not.
06:00:02.128 => Skipping
06:00:02.131 ------------------------------------------------------------ Processing [Media] share -----------------------------------------------------------
06:00:02.144 Primary storage: cache - size: 954GiB - used:  70 % (660GiB)
06:00:02.145 Secondary storage: user0
06:00:02.148 Share Information: Name: Media - Path: /mnt/cache/Media
06:00:02.150 Moving threshold: 70% (668GiB) ; Freeing threshold: 50% (477GiB)
06:00:02.150 Mover action: cache->user0 (cache:yes). Pool is above moving threshold percentage:   70% >= 70%.
06:00:02.151 => Will smart move old files from cache to user0. Nothing will be moved from user0 to cache
06:00:02.153 Skipping Files from List. File size are taken into account in the calculation of the threshold
06:00:02.153 List Path: /mnt/user/Files/ignore.txt:
06:00:02.197     Ignored files are using 359GiB
06:00:02.210 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-06-18T060001.list for Media

6 hours ago, Masterwishx said:

from list file :

`cache|user0|Media|yes|1750238329|512104247296|11925590110|1|1|6322601|/mnt/cache/Media/TVShows/The Expanse (2015) {tvdb-280619}/Season 01/The Expanse (2015) - S01E06 - Rock Bottom [Bluray-1080p Remux Proper][DTS-HD MA 5.1][AVC]-NOGRP.mkv`

here cache :prefer is used and this threshold for it (fillupThreshold="0" ), if "0" it should not move i think at all.

here: 70% >= 70% so all fine here .

06:00:02.084 Primary storage: cache - size: 954GiB - used:  70 % (660GiB)
06:00:02.085 Secondary storage: user0
06:00:02.088 Share Information: Name: ImmichMedia - Path: /mnt/cache/ImmichMedia
06:00:02.090 Moving threshold: 70% (668GiB) ; Freeing threshold: 50% (477GiB)
06:00:02.091 Mover action: cache->user0 (cache:yes). Pool is above moving threshold percentage:   70% >= 70%.
06:00:02.092 => Will smart move old files from cache to user0. Nothing will be moved from user0 to cache
06:00:02.105 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-06-18T060001.list for ImmichMedia
06:00:02.109 ----------------------------------------------------------- Processing [MakeMKV] share ----------------------------------------------------------
06:00:02.122 Primary storage: cache - size: 954GiB - used:  70 % (660GiB)
06:00:02.123 Secondary storage: user0
06:00:02.127 /mnt/cache/MakeMKV does not exist. Is the share still used? Consider removing /boot/config/shares/MakeMKV.cfg if not.
06:00:02.128 => Skipping
06:00:02.131 ------------------------------------------------------------ Processing [Media] share -----------------------------------------------------------
06:00:02.144 Primary storage: cache - size: 954GiB - used:  70 % (660GiB)
06:00:02.145 Secondary storage: user0
06:00:02.148 Share Information: Name: Media - Path: /mnt/cache/Media
06:00:02.150 Moving threshold: 70% (668GiB) ; Freeing threshold: 50% (477GiB)
06:00:02.150 Mover action: cache->user0 (cache:yes). Pool is above moving threshold percentage:   70% >= 70%.
06:00:02.151 => Will smart move old files from cache to user0. Nothing will be moved from user0 to cache
06:00:02.153 Skipping Files from List. File size are taken into account in the calculation of the threshold
06:00:02.153 List Path: /mnt/user/Files/ignore.txt:
06:00:02.197     Ignored files are using 359GiB
06:00:02.210 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-06-18T060001.list for Media

This series was imported correctly. Since it was a series pack, it did get the cache to the threshold.

Disabling the "Synchronize Primary files to Secondary" option seems to make the mover behave properly.

What I thought that setting would do was copy all my cache only files on to the array for parity protection.

What it actually seemed to do was just always move everything off the cache every cycle and leave the cache only files alone.

3 hours ago, PSteger said:

What I thought that setting would do was copy all my cache only files on to the array for parity protection.

Yep, that's should be it

3 hours ago, PSteger said:

What it actually seemed to do was just always move everything off the cache every cycle and leave the cache only files alone.

This should not happened

3 hours ago, PSteger said:

What it actually seemed to do was just always move everything off the cache every cycle and leave the cache only files alone.

If you click on option to see help description or press F1 :

Only modified files since last sync will be synchronised

1 hour ago, Masterwishx said:

This should not happened

Hence, my confusion as all my new media was being sent to the array regardless of how full the cache was.

Edited June 20, 20251 yr by PSteger

On 6/16/2025 at 8:49 PM, alturismo said:

now ... when you are using cache prefer shares (array > cache)

on these shares, this will happen ...

which is in my personal opinion a ... mess ;) using shares array > cache ;) playing ping pong ... makes sense when you dont use mover tuning plugin to keep files on cache anyway ... nevermind.

overall, these are 2 different rules, depending on share setup

cache > array (regular)

array > cache (nonsense)

AH ok I don't have any shares that are array > cache. That explains why its not being re-primed after a move. Since I dont have any shares that move in that direction I suppose I can just ignore "Fill up/prime...." as whatever setting it has in there won't be doing anything anyways. Thanks for explaining it. It makes so much more sense now.

23 hours ago, SiG3L said:

You probably still have test mode enabled, turn it off.

AH got it. I though those messages were from the debug being turned on. I've disabled it now. Im guessing with it on it never actually moves anything it just tells you what it would have done. Is that correct?

The mover is working correctly now and , at 70% it moved till there was only 50% left. Ive been looking around but I couldnt figure out what is the logic of the files selected to be moved? For example is the 50% left on the cache considered the 50% of the newest files ? I don't have age-based moving setup. Does it randomly select the files that are not considered cache-only ? thanks.

5 hours ago, chowpay said:

Ive been looking around but I couldnt figure out what is the logic of the files selected to be moved? For example is the 50% left on the cache considered the 50% of the newest files ?

should be self explaing ?

12 hours ago, chowpay said:

Is that correct?

Yep, when test mode on, nothing is moved

12 hours ago, PSteger said:

Hence, my confusion as all my new media was being sent to the array regardless of how full the cache was.

It should synchronise not move, so if you think there is issue you can send debug.zip after synchronizing for I can check it

On 6/20/2025 at 3:04 AM, Masterwishx said:

It should synchronise not move, so if you think there is issue you can send debug.zip after synchronizing for I can check it

My previous debug.zip was with the sync setting enabled. Disabling the setting stops the issue I was having about everything moving regardless of thresholds.