1 hour ago, Masterwishx said:

You have set files 10 days old and 1024M size will be moved , so if this not meet even more 70% , nothing will be moved ...

I think I follow now - any variables I add (such as the file size, date) all must be met to move the files. So if I turn off all of those other variables and just leave the % of cache used, then it should trigger, I'm guessing.

14 minutes ago, plunderisley said:

then it should trigger, I'm guessing

Yep, but if you had set move all after 75% it should move all.

If you have any issues you can post your logs here or debug.zip i can check why its not moving ...

! Question for all Plugin Users !

is anyone interested to get option with "Unraid binary move" instead of "RSync" to move Files ?

Is there an easy or built-in way to instruct the mover to recursively delete left over empty directory structures after it moves all files off of cache drive to array?

I did a search through this thread but not finding any satisfactory solutions.

4 minutes ago, voidpointer said:

Is there an easy or built-in way to instruct the mover to recursively delete left over empty directory structures after it moves all files off of cache drive to array?

I did a search through this thread but not finding any satisfactory solutions.

Please read help description of options

Edited May 24, 20251 yr by Masterwishx

2 hours ago, Masterwishx said:

Please read description of options

Due to the lack of detail of your response, I'm not sure exactly what you're expecting me to do. However, if you're referring to the option in the Scheduler page to remove parent or orphaned directories, I already have that enabled and it doesn't seem to address the issue. Previous posts in this thread that I've found seem to indicate that this option only removes the immediate parent directory and does not walk up the parent directory tree removing other empty parent directories (which is my expectation in this case).

37 minutes ago, voidpointer said:

Из-за отсутствия подробностей в вашем ответе я не совсем уверен, чего именно вы от меня ждете. Однако, если вы имеете в виду опцию на странице Планировщика для удаления родительских или осиротевших каталогов, у меня она уже включена, и, похоже, она не решает проблему. Предыдущие сообщения в этой теме, которые я нашел, похоже, указывают, что эта опция удаляет только непосредственный родительский каталог и не проходит по дереву родительских каталогов, удаляя другие пустые родительские каталоги (чего я и ожидал в этом случае).

If you will click on Clean Folders option or press f1, you find in help description that new option was added in last version Top Folder that will remove Top-Level folder with all empty subfolders.

That's why I wrote in help section of plugin and asking here in thread:

Pleeeese read help description!!!

of options to understand the options and usage of plugin.

Edited May 24, 20251 yr by Masterwishx

14 minutes ago, Masterwishx said:

If you will click on Clean Folders option or press f1, you find in help description that new option was added in last version Top Folder that will remove Top-Level folder with all empty subfolders.

That's why I wrote in help section of plugin and asking here in thread:

Pleeeese read help description!!!

of options to understand the options and usage of plugin.

Thank you for pointing out the "Top Folder" option. I did review the documentation before posting, but since this feature was added in the latest update, I wasn't aware of it despite my efforts.

In community forums like this, it's helpful to remember that users might be working with different versions or might have checked documentation before recent changes. Providing specific information about where to find features (like you did by mentioning the F1 help screen) is much more useful than just directing people to read documentation they may have already reviewed.

I appreciate the pointer to the updated functionality and will check it out now that I know where to look.

40 minutes ago, voidpointer said:

much more useful than just directing people to read documentation they may have already reviewed.

Yep but there is no documentation exist for plugin only help description of options and update information that can be also useful to read for what was fixed and what was added as new functionality.

Can't work out why its hanging, can you add some additional debug for the part after mvlogger "cleaning up"?

Trying to figure out why mover tuning seems to be ignoring a large collection of files way over the set age limit. Looking at the log there are a bunch of files with 2months+ dates on them, yet mover is not moving them to the array.

Considering it's happening on a bunch of old files im wondering if this problem actually happened with the old version of the plugin and back when I was on unraid 6. Now im on unraid 7.1.2 with the new plugin and i've noticed it, but surely they should be moved regardless when theyre so much older.

Messed around and ran a few moves with different settings incase something else was bugging but no luck, still a bunch of old files sitting there while the drive is also over usage % set, even when lowering it.

Edited May 29, 20251 yr by cr4zy

23 hours ago, JoshUK said:

Can't work out why its hanging, can you add some additional debug for the part after mvlogger "cleaning up"?

As I posted in pm there is only two thing after clean up (Synching date to config and restore turbo write) so not sure what to debug here...

Better try it on like smb share without any other programs in use

Note:

Mover Tuning plugin will be using Unraid move instead rsync in next version that will avoid some issues of rsync that some users had...

Edited May 28, 20251 yr by Masterwishx

10 hours ago, Masterwishx said:

Note:

Mover Tuning plugin will be using Unraid move instead rsync in next version that will avoid some issues of rsync that some users had...

Can you provide an option to continue using the rsync method? I'm hesitant to switch back to the Unraid mover binary as it is a significant change from rsync and especially how hardlinks are currently handled with the mover tuning plugin.

Additionally, could you list the issues that users are observing that should be fixed with the binary vs rsync?

Thanks.

22 minutes ago, ronia said:

Can you provide an option to continue using the rsync method? I'm hesitant to switch back to the Unraid mover binary as it is a significant change from rsync and especially how hardlinks are currently handled with the mover tuning plugin.

Additionally, could you list the issues that users are observing that should be fixed with the binary vs rsync?

Thanks.

Sure I can.

I was thinking rsync not respect disks included/excluded in share setting but seems also move has it.

I found If you change disks included /excluded they still use what was setting befor. Until reboot

I think move is much faster than rsync, also maybe some issues with multilang names of files. Also was some complains from users for rsync that in move not exist. Not remember now exactly.

On 5/27/2025 at 8:28 PM, cr4zy said:

Trying to figure out why mover tuning seems to be ignoring a large collection of files way over the set age limit. Looking at the log there are a bunch of files with 2months+ dates on them, yet mover is not moving them to the array.

you have small gap between thresholds 5% , try increase it to at least 10-15% :

For example :

```

movingThreshold="50"

freeingThreshold="35"

```

20 minutes ago, Masterwishx said:

you have small gap between thresholds 5% , try increase it to at least 10-15% :

For example :

```

movingThreshold="50"

freeingThreshold="35"

```

I will change that and test later on.

I guess my assumption in how it worked was wrong, I had assumed any files older than the age set would be moved, as long as it was above threshold.

38 minutes ago, cr4zy said:

I will change that and test later on.

I guess my assumption in how it worked was wrong, I had assumed any files older than the age set would be moved, as long as it was above threshold.

You are right, but you have also freeing threshold. Please reas help descriptions or press f1 for understanding the treshholds functionality

Also you have warning if low gap between them

1 hour ago, Masterwishx said:

You are right, but you have also freeing threshold. Please reas help descriptions or press f1 for understanding the treshholds functionality

So I have that set because by the way it is described in the help is: Setting this to ( 0% ) means that the mover will continue until all data is moved off the cache pool.

If I set move above 40%, free to 0% and age of 35, does that.

1. Above 40%, moves everything until 0%

2. Above 40%, moves everything older than 35 days and leaves anything newer than 35 days

The way each setting interacts with another isn't so obvious in that case and hard to test all possible combinations without a collection of different dates and sized files.

Any chance anyone knows if this is related?

Noticed I have +20 shares that have appeared out of no where. Not sure where they came from or how to update/handle them. Any suggestions? (images)

My Unraid system keeps crashing after 10 minutes of being powered on. Not sure what's happening. If I disable all Dockers, it runs fine. I am slowly turning on Dockers 1 by 1 to see if I can identify the problem.

Unraid OS version: 7.0.1

3 hours ago, cr4zy said:

If I set move above 40%, free to 0% and age of 35, does that.

1. Above 40%, moves everything until 0%

2. Above 40%, moves everything older than 35 days and leaves anything newer than 35 days

The way each setting interacts with another isn't so obvious in that case and hard to test all possible combinations without a collection of different dates and sized files.

it will be 2/ as described

in my case, once > 85 % treehold, mover will start, sorting by age ... freeing down to < 60 %, annything < 45 days old will be kept on cache anyway, so in terms i have alot of fresh files, it may will only free down to 70 % as all other files are "newer".

Set to auto would result in 1/ ...

6 hours ago, cr4zy said:

So I have that set because by the way it is described in the help is: Setting this to ( 0% ) means that the mover will continue until all data is moved off the cache pool.

If I set move above 40%, free to 0% and age of 35, does that.

1. Above 40%, moves everything until 0%

2. Above 40%, moves everything older than 35 days and leaves anything newer than 35 days

The way each setting interacts with another isn't so obvious in that case and hard to test all possible combinations without a collection of different dates and sized files.

Should be 2

5 hours ago, Boy Kai said:

If I disable all Dockers, it runs fine

So should be related to docker then.

Mover plugin does not make shares, only move data

9 hours ago, ronia said:

Unraid mover binary as it is a significant change from rsync and especially how hardlinks are currently handled with the mover tuning plugin.

Had you issues with unraid move for hard links?