14 hours ago, Thorman said:

and it's category is warning so it was sending an email on every notification so I have disabled all warning notifications going to email until this get's fixed, which is very annoying.

If notify set to No or errorOnly, it should NOT send any notify, you sended diagnostic without debug enabled and can't find in syslog anything about plugin running.

Also you have set to run plugin every 5 min this is not good idea, can be plugin can't move all in this time, so you got notify it still running or you have another script also run plugin?

You need more gap between plugin runs...

You can send diagnostic with log, debug enabled (file and syslog) after some runs I can check it again. Also should be some info in syslog about plugin

21 hours ago, shodeira said:

I get the same notification every day at my schedule for mover tuning. It started on 13th Aug, never happened before. Build-in mover schedule is disabled, only mover tuning is active.

Do you run empty disk or remove share maybe at same time? Or age_mover status?

You didn't included syslog to diagnostic

4 hours ago, Masterwishx said:

If notify set to No or errorOnly, it should NOT send any notify, you sended diagnostic without debug enabled and can't find in syslog anything about plugin running.

Also you have set to run plugin every 5 min this is not good idea, can be plugin can't move all in this time, so you got notify it still running or you have another script also run plugin?

You need more gap between plugin runs...

You can send diagnostic with log, debug enabled (file and syslog) after some runs I can check it again. Also should be some info in syslog about plugin

The weird part is that it's still sending notifications when set to no and error only. I have previously changed it to an hour, 3 hours, 6 hours, and 12 hours and I still had the notification. I just changed it to an hour right before exporting the debug zip file but I have had debug logging enabled for a few days now so hopefully you can pinpoint what the issue is.

ca.mover.tuning-debug-20260818-1813.zip

On 8/17/2026 at 10:52 AM, Masterwishx said:

Do you mean privios version same behavior?

You can send me by pm the diagnostic (this not contain any sensitive data) :)

Or you can check settings and mover logs debug logs...

Yes, same behavior on previous version. It started happened some days prior to latest update, logs didn't go back far enough to see exactly when, but I know based on the files actually getting moved and about when that stopped. I will PM you debug logs.

Edited August 19Aug 19 by Iceman24

19 hours ago, Thorman said:

The weird part is that it's still sending notifications when set to no and error only.

Found in mover logs :

```

11:40:01.728 ----------------------------------------------------------------- Global settings ---------------------------------------------------------------

11:40:01.733 Using global (cache:yes) moving threshold: 90 %

11:40:01.736 Using global (cache:yes) freeing threshold: 50 %

11:40:01.738 Using global (cache:prefer) fillup threshold: 90 %

11:40:01.745 Age: Automatic (smart caching)

11:40:01.759 ATIME: yes

11:40:01.767 mover: already running

...

```

You have latest version but in syslog old version:

`Installing new package /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2026.06.24-x86_64-1.txz`

4 hours ago, Iceman24 said:

Yes, same behavior on previous version. It started happened some days prior to latest update, logs didn't go back far enough to see exactly when, but I know based on the files actually getting moved and about when that stopped. I will PM you debug logs.

OK ,i checked the diagnostic , you have all data from media share (keep on primary) :

03:40:01.335 Using global (cache:yes) moving threshold: 40 %
03:40:01.336 Using global (cache:yes) freeing threshold: 25 %
03:40:01.337 Using global (cache:prefer) fillup threshold: 80 %

cache|media|yes|1784793600|6857058039|31774043642|124965909504|1|4192366|keep on primary|/mnt/cache|none|media/TV Shows/Ransom Canyon (2025) {tvdb-443051}/Ransom Canyon (2025) - S02E01 - Hey There Cowboy [NF WEBDL-2160p][DV HDR10][EAC3 Atmos 5.1][HEVC]-Kitsune.mkv|f

I think you need to make more gap between moving - freeing thresholds (more than 15%) .... Like wrote in `Note:`

Okay, so I noticed this was happening when I added more data to my drive, which is irrelevant as this happened after this occurred, but perhaps more space usage over time prior to that took it over a cliff of breaking this.

I am now in a place where I needed to modify these numbers anyways, so I want data moved at 75% full now, instead of 40%, which creates quite a gap, but it would never be able achieve the 25% of the current setting, at best 65%, so should I leave the number at 25% anyways? Perhaps it doesn't matter that it won't reach it, it will just do its best?

7 hours ago, Masterwishx said:

Found in mover logs :

```

11:40:01.728 ----------------------------------------------------------------- Global settings ---------------------------------------------------------------

11:40:01.733 Using global (cache:yes) moving threshold: 90 %

11:40:01.736 Using global (cache:yes) freeing threshold: 50 %

11:40:01.738 Using global (cache:prefer) fillup threshold: 90 %

11:40:01.745 Age: Automatic (smart caching)

11:40:01.759 ATIME: yes

11:40:01.767 mover: already running

...

```

You have latest version but in syslog old version:

`Installing new package /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2026.06.24-x86_64-1.txz`

I have upgraded the plugin and still have the issue. The issue isn't that mover is still running when starting a new run, it's that it sends me a notification when it's explicitly told not to do so.

from the same log

```

11:40:01.728 ----------------------------------------------------------------- Global settings ---------------------------------------------------------------

11:40:01.733 Using global (cache:yes) moving threshold: 90 %

11:40:01.736 Using global (cache:yes) freeing threshold: 50 %

11:40:01.738 Using global (cache:prefer) fillup threshold: 90 %

11:40:01.745 Age: Automatic (smart caching)

11:40:01.759 ATIME: yes

11:40:01.767 mover: already running

11:40:01.788 Notify: no

...

Notify is set to no but I still get the notification, why would that be?

9 hours ago, Thorman said:

Notify is set to no but I still get the notification, why would that be?

I can't reproduce it, but will try to fix it, you can help with testing?

59 minutes ago, Masterwishx said:

I can't reproduce it, but will try to fix it, you can help with testing?

hmm for some reason the notification isn't happening now... I woke up and checked my notification tab and there was nothing there. If it comes back I will gladly help with testing.

On 1/15/2026 at 4:50 PM, VivianV said:

I'm sorry to be bothering, but the age filter doesnt seem to be working.

I noticed the mover not moving anything and ive played around with dozen different dry runs and figured out that any "Move files that are greater than this many days old:" set to anything else than Auto, will not move any files.

Ive checked with stat and find to see that unraid actually sees the files as older than 1 day. I have CTIME and ATIME off and everything else advanced off.

If i disable the age filter or set it to auto it works, but doesnt with anything else.

Just updated to newest version of plugin and unraid and the ui is finally better, but the age filter still doesnt work

Any ideas?

On 1/15/2026 at 4:50 PM, VivianV said:

I'm sorry to be bothering, but the age filter doesnt seem to be working.

I noticed the mover not moving anything and ive played around with dozen different dry runs and figured out that any "Move files that are greater than this many days old:" set to anything else than Auto, will not move any files.

Ive checked with stat and find to see that unraid actually sees the files as older than 1 day. I have CTIME and ATIME off and everything else advanced off.

If i disable the age filter or set it to auto it works, but doesnt with anything else.

Just updated to newest version of plugin and unraid and the ui is finally better, but the age filter still doesnt work

Any ideas?

Well I finally fixed this somehow by checking what the mover was actually doing and noticed that it had been running non-stop for god knows how long. Softstop did not work, but after a hard stop and a "move now" it just worked... No idea what was up with that, but now it works

For users that have plugin not moving data with thresholds!

Seems I found the bug, should be fixed in next version...

New version is out, fixed calculations for threshold pool used, users who used : 75% to 25% or any others, now should work correctly!

Will be cool to have feedback that is fine now :)

Good release thankyou! - forums wont let me react to your post.

Latest version 2026.08.29
Incorrectly calculating ignored files.
14:30:13.787 Skipping Files from List. File size are taken into account in the calculation of the threshold

14:30:13.787 List Path: /mnt/cache/appdata/scripts/mover_ignore_all.txt:

14:30:14.084 Ignored files are using 4.6TiB

Actual ignored files = 2.2TiB calculated using "du -sch $(cat /mnt/cache/appdata/scripts/mover_ignore_all.txt) 2>/dev/null | tail -1"

17 hours ago, srpage said:

Latest version 2026.08.29
Incorrectly calculating ignored files.
14:30:13.787 Skipping Files from List. File size are taken into account in the calculation of the threshold

14:30:13.787 List Path: /mnt/cache/appdata/scripts/mover_ignore_all.txt:

14:30:14.084 Ignored files are using 4.6TiB

Actual ignored files = 2.2TiB calculated using "du -sch $(cat /mnt/cache/appdata/scripts/mover_ignore_all.txt) 2>/dev/null | tail -1"

OK. I've discovered the issue. I am cross seeding torrent files that are hard linked. They are being double, triple counted in the calculations.
Any suggestions on how to fix?

Found the solution --> downgrade to 2026.08.21. Everything works again. (85% to 80% with 1TB Cache)

I tried working with different thresholds—no moves occurred (even at 100% → all containers/VMs got paused).

Changing it to “move based on age—1 day” triggered a move, but it's a useless alternative to “based on age: auto.”

LogFile (2026.08.29).txt

LogFile (2026.08.21).txt

Edited 14 hours ago14 hr by User_0815

2 hours ago, User_0815 said:

Found the solution --> downgrade to 2026.08.21. Everything works again. (85% to 80% with 1TB Cache)

I tried working with different thresholds—no moves occurred (even at 100% → all containers/VMs got paused).

Changing it to “move based on age—1 day” triggered a move, but it's a useless alternative to “based on age: auto.”

LogFile (2026.08.29).txt

LogFile (2026.08.21).txt

The solution to what?

It would be easier to help out if you shared your debug zip located at the bottom of the Mover Tuning settings.

Edited 12 hours ago12 hr by chodeus

On 9/2/2026 at 4:57 AM, srpage said:

OK. I've discovered the issue. I am cross seeding torrent files that are hard linked. They are being double, triple counted in the calculations.
Any suggestions on how to fix?

Yep, please check @chodeus pr on github

11 hours ago, User_0815 said:

I tried working with different thresholds—no moves occurred (even at 100% → all containers/VMs got paused).

Please send debug.zip