13 hours ago, DontWorryScro said:

I need CA Mover Tuning to completely ignore system, OS, and plugin files, especially anything inside /usr/local/emhttp/plugins. This folder should never be treated as share or user data. If there’s some way my settings could affect this, I’d be happy for advice, but I haven’t included any plugin folders in any shares.

I was rewrited code for shares with cache prefer in last version for this will never happen, but from debug I see for share (plex4k) :

find -type f -not -name '.placeholder' -.....

So it not include the share path here, and seems take current path.

Will try to fix it today if will have time

I'm still facing the issue, that mover with this plugin won't move nor sync files.

I have two ZFS pools, one primary with a single NVME and a secondary, which acts as long term storage. The NVME is primary, the second is secondary storage.

Mover should sync all files smaller or equal to 98 MB and move all files larger than 98 MB from primary to secondary

Thresholds:

Moving: 70%

Free-up: 60%

Fill-up to: 60%

I played with these numbers to no change. I am running one central configuration and not a per-share config. I tried that before, but also did not help.

Mover won't sync nor move new files that should be covered by the configuration. That extends to small files, which should be synced, but also to bigger files, which should be moved.

I can verify this by running rsync manually and see what is synced between primary and secondary.

Realizing this gives me the impressions that without running rsync manually, I do not have parity protection when this plugin controls mover.

ca.mover.tuning-debug-20251031-0843.zip

13 hours ago, DontWorryScro said:

Here you go. Thanks!

Found the bug, will be fixed in next version.

2 hours ago, Gymnae said:

Moving: 70%

Free-up: 60%

You need more gap between for move files, also read help options for sync files, it sync only when cache below thouse thresholds iirc

Also I added sync for shares override

Is it possible to update the plugin to support the new "emptying disk(s)" feature in Global Share settings?

This is very useful for moving data off of disks to change the filesystem without having to use something like unbalance which is extremely slow for me.

1 hour ago, johnsanc said:

This is very useful for moving data off of disks to change the filesystem without having to use something like unbalance which is extremely slow for me.

you can run it from cli

You can also configure that in UI now. Its listed in the documentation for how to migrate fileystems. I have to do that for XFS v4 to v5 for a few disks. I basically have to disable Mover Tuning for this type of move since it doesn't seem to support that feature.

Edited October 31, 2025Oct 31 by johnsanc

1 hour ago, johnsanc said:

to disable Mover Tuning f

you can run : mover start -e diskX or to run unraid mover : mover.old start -e diskX

Edited October 31, 2025Oct 31 by Masterwishx

1 hour ago, johnsanc said:

You can also configure that in UI now

if you mean in Global Share Settings then you need to stop array ?!

Yes its a very weird design choice to put it there... but that feature is available in UI shoved under Global Share settings as shown in my previous screenshot

1 hour ago, johnsanc said:

I basically have to disable Mover Tuning for this type of move since it doesn't seem to support that feature.

Oh you mean to add like in Unraid mover when run to empty disk if was set in option.

I saw they added code for it, now I got it.

Edited October 31, 2025Oct 31 by Masterwishx

I will check if I can add it, but you can still run in cli, or make force mover schedule that will run unraid mover

Yes for now i set "Move Now button follows plugin filters" to "no" to get the empty disk function to work.

On 10/30/2025 at 8:31 PM, DontWorryScro said:

I am experiencing a repeatable and serious issue using CA Mover Tuning

Please check new version, should be fine now, sorry for it.

1 hour ago, Masterwishx said:

Please check new version, should be fine now, sorry for it.

Confirmed fixed. Thanks for jumping on that so fast!

CA Mover Tuning does not seem to handle empty folder trees on cache

Steps to reproduce:

1. On the cache create an empty folder tree only, for example:

   mkdir -p /mnt/cache/testshare/1/2/3/4/5
   

   Do not put any files in it.

2. Make sure the share is set to use the cache and to be moved to the array (user0).

3. In CA Mover Tuning set all move thresholds to 0 so the mover will always run.

4. In CA Mover Tuning set Clean empty folders to Yes or to Top folder.

5. Run the mover.
   

The result is nothing is moved. The folder tree stays on the cache exactly as it was. It looks like the plugin just says there is no work to do because there were no files in that path.

I expect even if there are no files in the folder the plugin should still check that folder. The empty folder structure should be mirrored to the array (user0) as part of the move. After that, because Clean empty folders is enabled, the same empty folder structure on cache should be removed, including the top folder if that option is selected.

How it currently works, can (and does) leave lots of empty folders sitting on the cache that aren't moved/mirrored to the array. That is the exact thing the Clean empty folders and Top folder options are meant to clean up. Right now it only seems to clean when it has actually moved a file first.

Edited November 1, 2025Nov 1 by TrevP
added 2nd mkdir example

1 hour ago, TrevP said:

Right now it only seems to clean when it has actually moved a file first.

Yep this is how plugin work if you read help description of the option.

1 hour ago, Masterwishx said:

Yep this is how plugin work if you read help description of the option.

To me "move", means move everything. files and folders. If not, we are going to be left with a bunch of unmoved, not array protected folder structures.

Is it possible to add the following option:
Items to move ->
Files only : current default behavior
Files and Folders : Treat Folders just like files. Move them as well, even if the folder is empty.

27 minutes ago, TrevP said:

To me "move", means move everything

It should move everything by find function + plugin setting, you can enable debug and check this find function in debug log (should move also empty folders)

But when clean it clean folders of moved files.

Edited November 1, 2025Nov 1 by Masterwishx

3 hours ago, TrevP said:

The result is nothing is moved.

Please check help description of options by click on it or F1. To see how thresholds works 

Adjusting second media cache - reminder needed! So, ages ago I set up a second SSD as a media cache drive (in addition to the primary cache for apps etc) to hold recently downloaded TV for quick access. However the secondary cache is filling up and I can't remember how to change the rules for when data on it should be moved to the main array (e.g. by age or by how full the cache drive is).

I have the mover tuning plugin installed, but it's not obvious how to change settings for the secondary cache drive. Can anyone remind me? Thank you!

1 hour ago, Masterwishx said:

Please check help description of options by click on it or F1. To see how thresholds works 

I know how thresholds work. I have thresholds set to 0%; meaning move "everything".

The mover isn't moving folders that happen to have no files in them; it's ignoring them. I can recreate this every time as per the example I gave in my original post. Even a pure empty folder structure should be preserved and moved to the array for protection; the default behavior of the mover ignores empty folder structures; they are not moved across.

This is why I'm wondering if we could add an option to treat folders just like files; don't ignore them if they happen to be empty.

This is the config for a particular share with its own dedicated cache. Recently the cache filled up and the mover engaged. It moved everything to the array and I don't understand why. It's set to only move files greater than 300 days old. (And there was plenty of recent files)

9 hours ago, TrevP said:

I know how thresholds work. I have thresholds set to 0%; meaning move "everything".

You said it not moving files, that mean sometimes need gap between thresholds.

About empty folders I think it's how plugin worked always, do you had same experience with older versions?

You can open future request on github if so.