MrMatt

I think some of the confusion is there is 3 plugins with various fixes and features all named the same with the same icon. The support thread for them are all the same. Additionally, the newer forks that work with unraid 7 don't support the same simple operation of the original. All of this means people are asking for support and people are offering support, not knowing which version they are using. I know I was caught off guard by seeing some screen shots that didn't reflect the features in the original version I had installed at the time.

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!

I believe I solved the issue with mover running for a long time. I think it was due to having Docker as a directory instead of a vdisk. The directory had tons and tons of little files, many of which were hardlinked to many other files to keep the overall size down for duplicates. But this lead to the mover going through each file to figure out what it was going to do and taking a very long time. I switched back to a vdisk and the mover ran a dry run in only a few minutes. As for the second part, I guess it would be a one time issue, so maybe I'll just let the mover do what it wants and be done with it. Overall, I like the newer mover tuning plugin, just some things to be aware of.

Hello, I switched from the older Mover Tuning plugin to the one that supports v7 but I'm still on v6 for now. I've kicked off a manual move but it's been going for over 24 hours. I see the mover_tuning file growing in size. Is this expected? I love the auto age process but I was wondering if there's a way to skip the priming of the cache. It'll end up filling in anyways over time but I figure it's sort of silly to move stuff to the cache drives only for it to be moved off in a few days. Thanks