2 hours ago, ronia said:

but maybe something to look into if you have free time.  

Will try to check but will be better if you open issue for it 

4 hours ago, Masterwishx said:

No need to post syslog. 

You need to post files from /tmp/ca.mover.tuning. + config will try to add debug zip for diagnostic in next version 

reverted to 2025.04.05 and working fine for now

it seems that my cache has been flushed ???!!
As it is base on "old age", is it possible that files with less that 1 day old, are not moved ?

Can anyone tell me if i have this right? The way ive set it, it only moves stuff that’s older than 30 days IF 85% or more of the cache is full, right? The old mover tuning had a “force move it over xx% of cache” which i really liked bc that way if i have no files over 30 days old it wouldn’t keep them in cache if it got more full than 85% or whatever i set it to. 

2 hours ago, pleasehelpmeguys said:

Can anyone tell me if i have this right? The way ive set it, it only moves stuff that’s older than 30 days IF 85% or more of the cache is full, right? The old mover tuning had a “force move it over xx% of cache” which i really liked bc that way if i have no files over 30 days old it wouldn’t keep them in cache if it got more full than 85% or whatever i set it to. 

That second option is wrong.

 

The first line will cause the mover to trigger at 85% and the second line will cause the mover to free up space on the cache until 85%.

 

Thus, no files will move since your free down/prime up is the same as your threshold. 

 

@Masterwishx we must get this question every other day.  I propose that we set default values of 85% and 25% for these two options specifically.  I think this is better as users are likely expecting something to happen with default settings.  When the mover moves a large portion of their cache, but not all of it most will likely be able to infer what happened with the settings and adjust accordingly.

 

When nothing happens, then most either assume the mover is broken or have no idea which setting could be causing the behavior.  At least when something moves and perhaps more/less than they are expecting, then they should have a rough idea of which options to play with.

Edited April 27, 20251 yr by ronia

8 hours ago, ronia said:

When nothing happens, then most either assume the mover is broken or have no idea

For this I added help description in thresholds but very sad users don't read it

8 hours ago, ronia said:

I propose that we set default values of 85% and 25%

Sure I can add default values and warning if they are same

10 hours ago, pleasehelpmeguys said:

Can anyone tell me if i have this right?

I have one issue with the synchronize option. The problem is that if I have files synchronized and I delete a file via SMB from /mnt/user, the file is only deleted from the cache, but it remains in user0.

 

Same stuff with sonarr, e.g. 1080p ISO got downloaded, synchronized to array, then a 4K one appeared - sonarr would remove 1080p one, but only on the cache, and the one on the array still exist.

 

Is there a way to change this behavior?

 

//Edit: Regarding SMB, first delete is removing it from cache, then I can refresh and remove it again from array. But still, the situation for arrs exists.

Edited April 28, 20251 yr by silverkin

is possibile to get a setting for excluded dirs?

8 hours ago, PilaScat said:

is possibile to get a setting for excluded dirs?

what are you missing ?

 

Hello, the mover is no longer working for me.  I'm not sure when it started to fail, but it had to be some time in the last few days.  This is all I'm seeing in the logs:
 

Quote

May  1 22:49:39 tower root: ionice -c 3 nice -n 19 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover 
May  1 22:49:39 tower move: Mover Tuning Plugin version 2025.04.24a
May  1 22:49:39 tower move: 
May  1 22:49:39 tower move: Usage: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start [-e <disk_name>]
May  1 22:49:39 tower move:        /usr/local/emhttp/plugins/ca.mover.tuning/age_mover stop|softstop|status|reset
May  1 22:49:39 tower move:        <disk_name> must match pattern 'disk[0-9]*'
May  1 22:49:39 tower move: 
May  1 22:49:39 tower move: reset  - reset config file to default values and delete override config folder

 

/tmp/ca.mover.tuning/ is empty.  I have not made any changes to any configs at all in the past few months, so I'm not sure what started this.

4 hours ago, foomanjee said:

I have not made any changes to any configs at all in the past few months, so I'm not sure what started this.

What unraid version 6.12?

4 hours ago, foomanjee said:

so I'm not sure what started this.

Last version has cli mode fix that not worked befor at all. 

Please note this plugin is mostly developing for unraid v7. 

Also I don't have option to test on 6.12, only have test server with unraid 7.1rc3 where was tested. 

 

So be sure to update unraid we will have v7.1 next week

5 hours ago, foomanjee said:

so I'm not sure what started this.

I can try to fix but you should test it

Checked, It's maybe related to how emhttp on v7 run mover command or need more code rewrite and testing on 6.12 that I really don't have it. 

 

So you can use previous version. 

5 hours ago, foomanjee said:

tower root: ionice -c 3 nice -n 19 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover 

 

what the lines befor it ? somethink like : ` emhttpd: shcmd (113): /usr/local/sbin/mover start |& logger -t move &`

The only lines before it are "Starting Mover ..." and that's it.

Yes, I'm on unraid 6.12.14

Quote

May  2 06:00:01 tower root: Starting Mover ...
May  2 06:00:01 tower root: Options: 
May  2 06:00:01 tower root: ionice -c 3 nice -n 19 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover 
May  2 06:00:01 tower root: Mover Tuning Plugin version 2025.04.24a
May  2 06:00:01 tower root: 
May  2 06:00:01 tower root: Usage: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start [-e <disk_name>]
May  2 06:00:01 tower root:        /usr/local/emhttp/plugins/ca.mover.tuning/age_mover stop|softstop|status|reset
May  2 06:00:01 tower root:        <disk_name> must match pattern 'disk[0-9]*'
May  2 06:00:01 tower root: 
May  2 06:00:01 tower root: reset  - reset config file to default values and delete override config folder
May  2 07:00:01 tower root: Starting Mover ...
May  2 07:00:01 tower root: Options: 
May  2 07:00:01 tower root: ionice -c 3 nice -n 19 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover 
May  2 07:00:01 tower root: Mover Tuning Plugin version 2025.04.24a
May  2 07:00:01 tower root: 
May  2 07:00:01 tower root: Usage: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start [-e <disk_name>]
May  2 07:00:01 tower root:        /usr/local/emhttp/plugins/ca.mover.tuning/age_mover stop|softstop|status|reset
May  2 07:00:01 tower root:        <disk_name> must match pattern 'disk[0-9]*'
May  2 07:00:01 tower root: 
May  2 07:00:01 tower root: reset  - reset config file to default values and delete override config folder
May  2 08:00:01 tower root: Starting Mover ...
May  2 08:00:01 tower root: Options: 
May  2 08:00:01 tower root: ionice -c 3 nice -n 19 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover 
May  2 08:00:01 tower root: Mover Tuning Plugin version 2025.04.24a

 

 

Interestingly, manually running the mover seems to work fine, so it's definitely the way the mover is being called via the UI
 

Quote

root@tower:~# /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start
08:10:58.802 ***************************************************** Mover Tuning Plugin version 2025.04.24a ***************************************************
08:10:58.819 Log Level: 1
08:10:58.848 ----------------------------------------------------------------- Global settings ---------------------------------------------------------------
08:10:58.871 Using global (cache:yes) moving threshold: 30 %
08:10:58.885 Using global (cache:yes) freeing threshold: 25 %
08:10:58.900 Using global (cache:prefer) fillup threshold: 0 %

....and so on....

 

Edited May 2, 20251 yr by foomanjee

11 minutes ago, foomanjee said:

so it's definitely the way the mover is being called via the UI

Yep, so nothing I can do with it it hink

On 4/28/2025 at 11:44 AM, silverkin said:

Is there a way to change this behavior?

Is this how smb work? You need maybe write some script? 

On 5/4/2025 at 5:43 PM, Masterwishx said:

Is this how smb work? You need maybe write some script? 

It is not only for smb, the smb I can omit, the problematic thing are the 'arrs

On 5/2/2025 at 3:10 PM, foomanjee said:

Yes, I'm on unraid 6.12.14

 

Please check this fix : https://github.com/masterwishx/ca.mover.tuning/blob/36f42b781ca4ab85d8cbda105b7bbbce0d8fc7a5/source/ca.mover.tuning/usr/local/emhttp/plugins/ca.mover.tuning/mover.php

On 5/2/2025 at 3:10 PM, foomanjee said:

The only lines before it are "Starting Mover ..." and that's it.

what do you have in `/boot/config/dynamix/mover.cron` file and /etc/crond for mover? 

33 minutes ago, silverkin said:

It is not only for smb, the smb I can omit, the problematic thing are the 'arrs

If you think this plugin issue you can open issue in github 

I had "rebalance shares" enabled, updated to the latest version of the plugin, and it moved all my plugin files onto my cache.

I disabled that option and it seems happy now. Or at the very least it's not shifting my system files around and breaking things. 🙂