Should we get the older incompatible mover tuning plugin version formally added to the 'known issues' for v7.0.0 release?

Also could we possibly work with the 'fix common problems' code to highlight the issue for those who were unaware and have upgraded already i.e. before filling up other old plugin users cache pools? Maybe even consider the new automated unRAID patch mechanism to upgrade from old to new plugin versions although I saw a post above that might be conflicting? Just wondering how many other folks out there might've upgraded to v7.0.0 and not yet noticed their cache pools filling up and also have no idea why

Is it worth asking @Squid to temporarily add a warning to the top page for this thread?

 

In the meantime for anyone else just wanting an emergency quick fix on unRAID 7.0.0 - removing the old incompatible mover tuning plugin and running the stock mover should work before adding the newer fixed plugin version back and configuring it again.

On 2/8/2025 at 4:17 AM, Masterwishx said:

we can wait if no i can move it to my github and compile it but not sure if can handle along this project ... but prs will help ...

Yeah, a long time ago I added some functionality to this plugin and had the intention of probably taking it over once hugenbdd was planning on moving on. Eventually I decided I would rewrite the plugin from the ground up because the code was starting to become janky implementation slapped on top of more janky implementations and it was just getting too messy to even consider adding more advanced functionality. I progressed pretty far but graduated and got a full-time job as a robotics engineer and never touched it again...that was about a year ago. Turns out it's really hard to have spare time / effort and energy when you have a full-time job lol. I've got a lot of respect for the people that seem to have a million side projects and somehow balance them with a good work-life balance.

 

I would like to pick up my development again because I had a lot of fun doing it, but I probably won't publish it because I can't commit to maintaining it and there are so many changes for me to go back and read. It's more of a class / object oriented approach so additional functionality can just be added in quite easily. I need to learn how to write tests for it because doing manual testing is so killer and wastes so much time, but having to write tests is also time consuming and not very motivating.

1 hour ago, Swarles said:

I would like to pick up my development again because I had a lot of fun doing it,

would be great

 

i even wrote myself a "simple mover" plugin for now, abusing the ignore function from mover tuning (which works) as i didnt wanted to replace the buildin mover ... but mine is mainly designed for media moving ... way more simple, but fast

 

lets see what time brings

 

Also in pr added the new option for Clean ZFS dataset that unraid mover make by default ...

might be time to just publish your fork, but only post a link here for manual installation until a confirmation from Reynald comes through, then if he decides to hand it over the link in the Community apps can be updated too. same for any other devs that would be willing to take it on longer term.

 

I have manually made some of the changes to my plugin files on the system, but as soon as I reboot it's going to pull the unmodified version again.

Edited February 11, 20251 yr by Faceman

On 7/31/2024 at 12:38 AM, Reynald said:

  

Yes it is:
 

The tuner list all files from cache:prefer and cache:yes from the more recent to the oldest, then it compare the cumulative size to the threshold, for each sharepool.

If you want to keep below 80% and that while running the scheduled mover you are at 92%, then the oldest files from cache:prefer and cache:yes representing 12% of space will be moved to array.
If you want to keep below 80% and that while running the scheduled mover you are at 67%, then the most recent files from cache:prefer shares on array, representing 13% of cache size, will be moved to cache, not those from cache:yes because they are meant to be moved from cache to array and that is.. 

I recently ran into an issue with Mover Tuning after upgrading Unraid to 7.0, so I came across this post. However, even after doing a dry run, I still noticed some problems.

 

To give a bit of background, I have two cache pools: `cacheos` and `cachemeta`.

 

`cacheos` is used to store `/appdata`, `/domains`, `/supports`, and `/system`. I have set the Primary storage to `cacheos`, Secondary storage to `array`, and enabled "Secondary storage to Primary storage." My requirement for `cacheos` is that as long as usage doesn’t exceed my set limit (90%), Mover should not move any files off the cache, and it should transfer any files from the array back to the cache.

 

`cachemeta` is used for download caching and storing small media files like .nfo files and movie posters. The Primary storage is `cachemeta`, Secondary storage is `array`, and I have enabled "Primary storage to Secondary storage." My requirement for `cachemeta` is that any file larger than 20MB should be moved to the array.

 

Mover works fine for `cachemeta`, but I'm running into a lot of issues with `cacheos`. Even when there's still plenty of space available in cacheos, Mover keeps trying to move files to the array—things like font files in `/support`, LLM models and database files in `/appdata`, and even my docker.img.

 

I'm not sure how to fix this. I’ve also tried disabling Mover Tuning in the schedule settings and setting individual Mover options for each share, but the issue persists. I’ll be uploading syslog.txt as well.

syslog.txt

Hi all,

 

Just upgraded to 7 and noticed mover tuning isn't working. Just doesn't seem to move anything at all. I used a script at runtime to only move stuff that's older and keep the rest at a specific disk size.

 

Is there anything at the moment that can be replaced with? Or is there an update in the works?

There are updates in the works, but what version are you on? most people having an issue of "no moving at all" are on the much older version that has not had an update since 2023,  if you have V 2024.09.05.0222 by Reynald, most functions do work on 7 with a few bugs being ironed out slowly.

2 hours ago, Faceman said:

There are updates in the works, but what version are you on? most people having an issue of "no moving at all" are on the much older version that has not had an update since 2023,  if you have V 2024.09.05.0222 by Reynald, most functions do work on 7 with a few bugs being ironed out slowly.

 

Yeah, that's the one I had installed (2023 one). All I'm using mover tuning for is to run a pre-script and whitelist files from a .txt that's it. Would this 2024 version work for that? Don't really use any other options

the newer version has the ability to use a whitelist and pre/post scripts so with some tweaking that should get the job done for you.

 

 

3 hours ago, Faceman said:

the newer version has the ability to use a whitelist and pre/post scripts so with some tweaking that should get the job done for you.

 

 

 

Thanks mate! What exactly isn't working at the moment though?

all covered very well in this thread but there are some bugs with shares with spaces in the name and some trouble with hardlinks.

 

 

 

 

So how many forks just got created? Can we all try to agree on one? In the previous page I count at least two right now: @Masterwishx and @the_lucifer

Edited February 12, 20251 yr by Moniker_30
Pinged wrong second person

17 hours ago, Sptz87 said:

Is there anything at the moment that can be replaced with? Or is there an update in the works?

if you need a simple solution, may take a look at "simple mover", still need some polishing, but doing its job here already.

 

running (currently) side by side with mover tuning (just to exclude ...), but as this turns out (sadly) i ll disable the regular mover as option in my next release.

 

it has 2 Options

 

- age, size, treehold setup move from Folders to array

or

- age only and move all from given Folders after x days.

 

sample config ... BUT, regular designed (for me) as Media mover ... as i only move media from cache to array

 

3 hours ago, Moniker_30 said:

So how many forks just got created? Can we all try to agree on one? In the previous page I count at least two right now: @Masterwishx and @the_lucifer

 

if @the_lucifer planning to maintain the plugin ? i can move my pr to him github , if not i can publish my version

I miss a feature i sued in the "old" mover tuning.

 

"Based on age"

 

So i dont use the "Schedule" but i use age. I that possible to get into the new "mover tuning" ?

 

Compiled new version with : 

 

- Fix issue for shares with spaces.

- Add option to clean ZFS datasets. 

 

https://github.com/masterwishx/ca.mover.tuning

 

I can maintain plugin until plugin Author is back or other user want to maintain or @the_lucifer confirm to maintain the plugin  

Can also post to CA Application if needed ...

Enjoy

 

Updated XML for Mover Tuning Plugin it will be in CA after some time , please remove old and install it ,

all configs are same , only one option added "Clear ZFS datasets".

Edited February 13, 20251 yr by Masterwishx

4 hours ago, DanielPT said:

"Based on age"

there is option days old

12 hours ago, alturismo said:

if you need a simple solution, may take a look at "simple mover", still need some polishing, but doing its job here already.

 

running (currently) side by side with mover tuning (just to exclude ...), but as this turns out (sadly) i ll disable the regular mover as option in my next release.

 

it has 2 Options

 

- age, size, treehold setup move from Folders to array

or

- age only and move all from given Folders after x days.

 

sample config ... BUT, regular designed (for me) as Media mover ... as i only move media from cache to array

 

Ok, I feel dumb but how/where can I find this plugin? I can't find it on the community apps tab on my box.

Edit: Sorry, I realized it's because I'm running an older version of unraid on my main box and the plugin's min version is 6.12.13. Ignore me!

Edited February 12, 20251 yr by MrMatt

9 hours ago, Masterwishx said:

Compiled new version with : 

 

- Fix issue for shares with spaces.

- Add option to clean ZFS datasets. 

 

https://github.com/masterwishx/ca.mover.tuning

 

I can maintain plugin until plugin Author is back or other user want to maintain or @the_lucifer confirm to maintain the plugin  

Can also post to CA Application if needed ...

Enjoy

 

I uninstalled the old plugin and installed @Masterwishx updated version and it seems to be working well! 

Thank you

12 hours ago, Masterwishx said:

there is option days old

Awesome and thank you.

 

Only question I have is can I have clarification of what the "Clean empty folder" option does?  

From what it reads, if you don't have it turned on, Mover will leave an empty folder for every group of files it moves?

7 minutes ago, DevanteWeary said:

Mover will leave an empty folder for every group of files it moves?

Yep, if it will be on it will remove thous empty folders. 

 

Also added Clean ZFS dataset, to remove them like unraid mover do it

6 hours ago, DToX_ said:

Thank you

Thanks for your fix 

15 hours ago, Masterwishx said:

Updated XML for Mover Tuning Plugin it will be in CA after some time , please remove old and install it ,

all configs are same , only one option added "Clear ZFS datasets".

Awesome, thank you!!

 

The "original" 2024 version now shows it's got an update as well for me?