4 minutes ago, Masterwishx said:

So if you install new version with current settings you have error?

Anyway I will fix it in new version and maybe will remove this part (with renaming cron file) as another fix avaliable in last version for crond

Yes. Same settings. If I run the update, it stops working.

And if I remove it and reinstall, reapply the settings, it also won't work.

It seems to be a combination of settings. If I install the new version with the default settings it does work.

Again, thx for your work! Plugin solves a lot.

Edited June 13, 20251 yr by Marcvz

18 minutes ago, Marcvz said:

It seems to be a combination of settings

Just in case maybe you tryed reset settings?

Just so you know it's not an isolated case, I have the same issue when I have the following set:

Logs show:

This impacted standard hourly moves and the 'Move Now' button. I have mover tuning set to run hourly, but runs weren't occurring.

/tmp/ca.mover.tuning has no new logs since June 10, there were no changes to my setup other than updating to 2025.06.07, no changes to my mover tuning settings have happened in a month or so until now due to noticing this issue.

Disabling force moving on a schedule allows the non-forced hourly moves to occur.

Does the force move cron schedule allow standard moving to work for anyone on 2025.06.07?

26 minutes ago, SakabaRihiro said:

Disabling force moving on a schedule allows the non-forced hourly moves to occur.

I will check it

28 minutes ago, SakabaRihiro said:

Does the force move cron schedule allow standard moving to work for anyone on 2025.06.07?

This should run mover.old not related to age_mover

1 hour ago, Masterwishx said:

This should run mover.old not related to age_mover

Apologies, I phrased that poorly.

What I meant to ask is if moving on a schedule works for anyone who has 'force move cron schedule' enabled.

I know that the force move should run mover.old, but having the force move on a cron schedule enabled is what causes age_mover to fail for me.

12 minutes ago, SakabaRihiro said:

I know that the force move should run mover.old, but having the force move on a cron schedule enabled is what causes age_mover to fail for me.

Yep I got it, this should not happen, I will check it

37 minutes ago, SakabaRihiro said:

I know that the force move should run mover.old, but having the force move on a cron schedule enabled is what causes age_mover to fail for me.

will be fixed in new version

Thanks, any idea what caused the bug?

Checked my friends server, and it's happening for them as well (also on 2025.06.07 using the same cron schedule), but not my backup server with 2025.05.23.

2 minutes ago, SakabaRihiro said:

Checked my friends server, and it's happening for them as well (also on 2025.06.07 using the same cron schedule), but not my backup server with 2025.05.23.

Some old code + new code coused issue ... i pushed to github if interesed : https://github.com/masterwishx/ca.mover.tuning/pull/71/files

43 minutes ago, SakabaRihiro said:

, but not my backup server with 2025.05.23.

Every update im trying to fix bugs and add new futures so ....

2025.06.14 version Update

- fix: Fix age_mover is missing the "start" parameter in the cron schedule when force move is enabled. **_(masterwishx)_**
- fix: Remove renaming of "mover.cron" to "mover.cron.disabled". No longer necessary with previous version.

Edited June 14, 20251 yr by Masterwishx

Hi

I seem to still have empty folders being left behind by the mover. I had this issue previously and I read that it was because the old plugin (uninstalled a while ago was the issue). I changed to the new mover plugin and deleted all the empty folders, however I just noticed this issue again.

Unraid Version 7.1.3 2025-06-04

CA Mover Tuning - masterwishx - 2025.06.07

Next time it happens let me know if you want to post some logs etc. I know how to post all the relevant screenshots with settings and share setup etc. But I don't know how you would want to prepare the logs etc, so I would need some basic guideance for that bit.

Thanks for the plugin

Mike

Edited June 14, 20251 yr by kiwijunglist

14 minutes ago, kiwijunglist said:

however I just noticed this issue again.

What is current settings?

Hi

Actually i just noticed there is now an option in the plugin to remove empty folders I just enabled that.

I have also noticed that sometimes the plugin will duplicate a file so I have the file in the cache and the array after a move and it doesn't move all the files sometimes. NB: all dockers access the files using the share ie: "/mnt/user" there is not mix of shares and direct access (ie /mnt/<drive_name>/).

I just updated as well.

TV Shows are downloaded to download_share on a cache

When TV Show is imported it is removed from the download client and the TV Show is moved into tv_share which initially is on the same cache_drive, but periodically the cache_drive is emptied onto the array for long term storage.

I havn't noticed any issues with mover until I've moved to unraid 7.

Mover Tuning Plugin Settings: (i just enabled the clean empty folders setting, but previously it was not enabled)

This is a duplicated file from the mover:

This is the shares setup:

TV Share Settings:

Download Share Settings:

Main view of array / share drives:

Edited June 14, 20251 yr by kiwijunglist

More worrying I also noticed that the mover has someone deleted a file. I ran the mover again and it deleted game of thrones S06E09 in the above, it is gone from the samsung_pro and it is not on the array anymore.

ca.mover.tuning-debug-20250615-1017.zip

Edited June 14, 20251 yr by kiwijunglist

20 hours ago, SakabaRihiro said:

I know that the force move should run

On 6/13/2025 at 10:32 PM, Marcvz said:

If I install the new version with the default settings it does work.

Check new version

7 hours ago, kiwijunglist said:

I have also noticed that sometimes the plugin will duplicate a file so I have the file in the cache and the array after a move and it doesn't move all the files sometimes

This should not happen, I will check your debug.zip

7 hours ago, kiwijunglist said:

it is gone from the samsung_pro and it is not on the array anymore.

You can check Rsync or move what work better for you.

But folders deleted after files was moved and if only empty folders...

5 hours ago, Masterwishx said:

Check new version

It works again! :)

Thanks a lot!

Edited June 15, 20251 yr by Marcvz

"This plugin modifies stock system files and may cause issues with your system"

So how save is this to use these days on 6.12.6 version?

2 hours ago, ralop said:

"This plugin modifies stock system files and may cause issues with your system"

This plugin rename mover to mover.old for it can be runned by mover , that's all.

Unraid mover also had/has bugs that was/will be fixed so...

Just try it.

Edited June 15, 20251 yr by Masterwishx

Trying to understand how this works and its little confusing to me (n00b).

My filter settings are here:

Here is how I read what will happen:

1. once my cache gets to 70% it will attempt to move stuff to the array, basically this is what triggers mover ca

2. Even though it will get triggered at 70% it will always keep at least 50 % of the data in cache

3. The mover will move data back to cache until its up to 80 %

What I see happening is this :

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

Currently my cache sits at 78% so I'm wondering what this notification is actually four and once I get over 80% cache should it then stay that way all the time and mover is just moving things to keep it at 80%

Am I totally misunderstanding the help hints? TIA

1 hour ago, chowpay said:

Am I totally misunderstanding the help hints? TIA

nope, but depends how your shares are setup ...

1 hour ago, chowpay said:

1. once my cache gets to 70% it will attempt to move stuff to the array, basically this is what triggers mover ca

basically the scheduler is triggering, using the settings from plugin

1 hour ago, chowpay said:

1. Even though it will get triggered at 70% it will always keep at least 50 % of the data in cache

exactly

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

1 hour ago, chowpay said:

1. The mover will move data back to cache until its up to 80 %

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)

@Masterwishx if I want to run the mover manually what arguments can I provide to age_mover to simulate as if the "move now" button were pressed? Is this possible?

The reason I want to do this, is I want to write a small script that essentially hits the "Move Now" button whenever disk utilization is above a certain value.