3 hours ago, ronia said:

I'm having issues in general with the mover.  I didn't have Reynald's installed prior to unraid 7, so I'm not sure if this is a setup issue or a bug with the mover tuning plugin and v7.

 

It seems to be ignoring the share's mover action.  This particular share is setup as such:

 

 

however, the mover seems to be trying to move it from my cache drive to the array:

Jan 12 03:51:27 Dammerung move: Moving "/mnt/cache/./data/workspace/scripts/ffmpeg-2024-11-18-git-970d57988d-full_build/LICENSE" to /mnt/user0/ Jan 12 03:51:28 Dammerung move: 1813 files remaining from caches to array 569GiB

 

In fact, it tried moving my appdata to /mnt/user0 as well until I dropped the array from the secondary storage.  

Just chiming in to say I had the same issue.  Had the old plugin, realized after updating to 7.0 there was an updated version, updated and ran it, and had it erroneously think it needed to move files from my cache, with the same weird /./ folder in the path, to /mnt/user0/  

 

Moving "/mnt/cacheb/./metadata/cache/images/resized-images/3/369d47f7-c93c-b97a-e8a6-d04f0d6cf13b.jpg" to /mnt/user0/  

/metadata is a folder directly on cacheb without any /./ folder in between, and these files were not actually being moved by the mover, they remained on the cache at the same location despite no error message saying the move failed.  I use this "cacheb" to store things like thumbnails and various small files, so it was trying to move ~700,000 files one at a time and probably would have taken more than a week to go through.  

 

For the moment I've just removed the mover tuner plugin and am using the regular one, which runs fine and doesn't try to touch/move those files.  

23 hours ago, Faceman said:

This version hasn't had a bugfix for a few months, Dev is back and will be working on it again soon.

 

the empty folders aren't going to cause any issues, and they should be able to be cleaned up once the script is fixed.

Thanks. Looking forward to the fix 

Seeing this error when I try to run the mover, any ideas:
 

Jan 13 13:47:31 <redacted> emhttpd: shcmd (635638): /usr/local/sbin/mover start |& logger -t move &
Jan 13 13:47:31 <redacted> move: Log Level: 1
Jan 13 13:47:31 <redacted> move: /usr/local/sbin/move does not exists, creating soft link
Jan 13 13:47:31 <redacted> move: ln: failed to create symbolic link '/usr/local/sbin/move': File exists
Jan 13 13:47:31 <redacted> move: mover: started
Jan 13 13:47:31 <redacted> move: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 206: /usr/local/sbin/move: No such file or directory
Jan 13 13:47:31 <redacted> move: cat: write error: Broken pipe
Jan 13 13:47:31 <redacted> move: mover: finished

 

What version of the plugin do you have? that looks like it might be the old version if it cant find the mover script

On 12/6/2024 at 6:19 AM, alturismo said:

if its a seperate share ... yes

 

inside the share settings, scroll a little down

 

 

would always move like without mover tuner ...

 

Edit, sorry, there you set your individual settings for this Share ...

There should be a 0% option on the Scheduler page. Minimum is 5%.

I like one of the users here always have data coming in and want to move them to the array as soon as the scheduler triggers. On the old plugin version it would move everytime but updating to the new version of the plugin, I have to wait until it hits 5% or manually trigger.

Why not have a global setting? Kind of sucks to have to do it on every share

4 minutes ago, Kloudz said:

There should be a 0% option on the Scheduler page. Minimum is 5%.

I like one of the users here always have data coming in and want to move them to the array as soon as the scheduler triggers. On the old plugin version it would move everytime but updating to the new version of the plugin, I have to wait until it hits 5% or manually trigger.

Why not have a global setting? Kind of sucks to have to do it on every share

I modified the tuning file and manually set the threshold to 0. This modification resolves my issue. I no longer have to wait for the cache drive to fill up 5% to be considered to move.

0% should definitely be in global setting

when I have "Synchronize Primary files to Secondary", even if I don't reach the MOVE threshold (>=80%) shouldn't the mover COPY new files from cache to array instead of MOVE? It always moves files...

Edited January 14, 20251 yr by Jarek Kr

18 hours ago, Kloudz said:

I modified the tuning file and manually set the threshold to 0. This modification resolves my issue. I no longer have to wait for the cache drive to fill up 5% to be considered to move.

0% should definitely be in global setting

I did the same thing. But would definitely like it better when there is 0% option in the Global settings for the plugin.

I might have found unwanted Mover Tuning behaviour - I run Unraid 7.0.0 and Reynolds Mover Tuning both in the current version.

I want the mover to start moving when the cache is filled to a certain level, but not empty it completely.

 

The settings are:
 

- Only move if above this threshold of used Primary (cache) space: 50%
- Free down/prime up to this level of used Primary (cache) space:  30%
- Move files off Primary (cache) based on age?                     No
- Move files that are greater than this many days old:             Auto

All advanced options are on default (which is No...).

 

The mover checks hourly if the threshold to start moving is reached, and only moves, when this is the case. So far, so good.

But it empties the cache completely, which is unexpected.

 

It works, however, when 'Move files based on age' is set to 'yes'.

 

If this behavior is intended, it would be nice to give a hint in the interface, as the 'Free down/prime...' lower threshold is effectively disabled when 'Move files based on age' is set to 'yes'.

 

Other than that - I am fairly new to Unraid, this plug-in is the first for me and it's fantastic - great job!

 

 

 

 

Set the move based on age setting to true. it doesn’t know what files to move and what to keep without that setting enabled. yes I think that should be worded better in a future update.

 

and also enable advanced settings and check that you dont have a move-all threshold set.
youc an also check that you havent got any mover tuning overrides set on a per share basis, in each shares settings you can add optional separate thresholds and settings to have some shares empty completely and some keep files.

HI I have a situation where I am using the Reynald age_mover in 6.12.14

I have checked all shares no override.

When the mover runs it finds that once of my primary cache is 92%, and says it will smart move old files from (cache) to user0, and says updating filtered file list.  It completes and it moves nothing.  If I go into the Mover_action file it says "keep on primary" for all the files and hence moves nothing.  This is a tad of a problem because my primary cache is now 92% and I don't want to evacuate 2TB of files like the old mover did.

 

How do I fix, thx.

 

Example from one of the shares:

 

18:48:48.991 ----------------------------------------------------------- Processing utilities share ----------------------------------------------------------
18:48:49.013 Primary storage: sata_ssd_cache - size: 1.9TiB - used:  92 % (1.7TiB)
18:48:49.015 Secondary storage: user0
18:48:49.021 Share Information: Name: utilities - Path: /mnt/sata_ssd_cache/utilities
18:48:49.027 Moving threshold: 90% (1.7TiB) ; Freeing threshold: 65% (1.2TiB)
18:48:49.029 Mover action: sata_ssd_cache->user0 (cache:yes). Pool is above moving threshold percentage:   92% >= 90%.
18:48:49.032 => Will smart move old files from sata_ssd_cache to user0. Nothing will be moved from user0 to sata_ssd_cache
18:48:49.039 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-01-16T184845.list for utilities

 

 

Settings for mover:

 

You don't have test mode turned on do you?

 

I checked, not in test mode:

 

override settings on the share settings page perhaps? and maybe go in and find that filtered list file and have a look at it, then delete it. it shouldn't be doing any filter/ignore stuff with that setting set to no.

 

Otherwise, i'd say to try removing the plugin and re-installing because something is a bit off there.

Hi there, same issue since version 7.0.0, mover no longer working

 

EDIT :

 

So

Workaround:

 

I saw mover errors in log.

 

Uninstall a plugin named "CA Mover Tuning" and try to reinstall it but no longer exist on the app store. 

I installed instead "Mover tuning" (btw there is a plugin with the same name and version)

 

Less option than the previous but it's fine. 

 

I lower the thresold to 25% to test. 

(it's at 42% full)

 

Now I can see lots of entries in log about mover action (mainly Plex cache since 1 hour)

 

It's still at 42% (1Tb cache) and mover is still running. 

 

So I guess with version 7.0.0 an old forgotten plugin is now longer working. 

 

EDIT: 

cache now normal state (7% full)

 

 

 

Edited January 19, 20251 yr by Tarnous

On 1/18/2025 at 3:13 AM, Faceman said:

override settings on the share settings page perhaps? and maybe go in and find that filtered list file and have a look at it, then delete it. it shouldn't be doing any filter/ignore stuff with that setting set to no.

 

Otherwise, i'd say to try removing the plugin and re-installing because something is a bit off there.

 

Thanks.  I did say I didn't have any override and I started looking at the code (I thought maybe it was an easy fix).  A few items:

 

1. Share override.  If you have a share overrride the code injects a file with the share name in:  /boot/config/plugins/ca.mover.tuning/shareOverrideConfig/$SHARENAME.cfg

Since there are no files in here I would assume that that part of the code is working (as I have no share overrides)

 

2.  The remove the files in the tmp suggestion won't work because with every run of the mover script it creates new files so its a runtime generation tmp file creation.

 

3.  I could reinstall, but looking at the code, it is running the existing code base and I also ran it from the command line with the same issue so it would be isolated to the script not any of the plugin integration.  

 

4.  I am going to concentrate on the emit from the Filtered Files (which seems to be correct but I will doublecheck FS) and the Mover_action which emits "keep on primary" for 100% of the files (meaning nothing happens)

 

Note: I am still on latest v6 so I cannot say if this is a v7 issue also.

 

OK,

 

I read through the code and figured it out after injecting some custom logging.  The code only checks active shares, not passive ones so I had a passive directory (meaning not active) that was taking 400GB and the script was not calculating for it.  Rather than try and fix I used the unbalance plugin to move the files off the then active share and repointed the share to the non-active cache and voila it is working now.

 

So be aware if you have files in a cache drive and they are not active in the share definition but still under shfs the mover plugin will not account for files that are not listed in the active share.

 

So for instance my active share was NVMe (cache)->array and I had files in the SSD cache (not active).  The SSD cache was at 92% so it was not taking into account those files because it was only reading the active share config.

On 1/14/2025 at 6:29 AM, Jarek Kr said:

when I have "Synchronize Primary files to Secondary", even if I don't reach the MOVE threshold (>=80%) shouldn't the mover COPY new files from cache to array instead of MOVE? It always moves files...

I had this same issue which was resolved for me by deleting /boot/config/plugins/ca.mover.tuning/shareOverrideConfig/$SHARENAME.cfg for shares which had issues. Even thos setting in that override is no it still breaks sync for some reason.

I am using the age tuner, with the "reverse mover" config in the share setup (array->cache). 

 

Under the old mover, you could manually run find and pipe it to move. But that does not seem to work in the new mover/tuner. Is there any way to move a specific file or subdirectory ignoring other mover rules to free up space? (eg, I expect to download some very large files that will overfill my cache, so I want to drain some, but not all of the existing cache)

longstanding bug that one. will probably be first to be looked at now that the dev is back.

 

 

 

Im looking into upgrading to 7.0.0 but alot of ppl have problems with this plugin.

 

But i have the "Old" version installed? Can i just remove it and use the "new" one? Or is it the same? Sorry im a little confused

 

You can totally uninstall the old one and install the new one. You'll have to redo your settings. But I must warn you that there is a lot of issues with the new one. The old one will not work under Unraid 7

10 minutes ago, foux said:

You can totally uninstall the old one and install the new one. You'll have to redo your settings. But I must warn you that there is a lot of issues with the new one. The old one will not work under Unraid 7

Okay thanks! I will upgrade to 6.12.15 until it is okay to upgrade  

Hi all, first post on the forum. I got a TerraMaster F6-424 Max with a 78 TB array and a 4 Tb NVME SSD. Everything is setup according to the trash-guides.

 

I would like to keep the /mnt/user/data/music folder always on cache, and the reste of /mnt/user/data on array (but cached as per the array settings).

 

Does this plugin allow me to do this? 

 

Thanks!

38 minutes ago, noworthwhile said:

Does this plugin allow me to do this? 

 

Thanks!

Yes. Just put the folder in your list of ignored files