Hi all, I found an issue where the mover would not move files for user shares that have spaces in the name.

Examples: "TV Shows", "TV Shows UHD", "Movies UHD"

Error Log:

Quote

---------------------------------------------------------- Processing TV Shows UHD share --------------------------------------------------------
Primary storage: cache_downloads - size: 1.9TiB - used:  86 % (1.6TiB)
Secondary storage: user0
Share Information: Name: TV Shows UHD - Path: /mnt/cache_downloads/TV Shows UHD
Moving threshold: 50% (932GiB) ; Freeing threshold: 35% (653GiB)
Mover action: cache_downloads->user0 (cache:yes). Move All from Primary->Secondary shares option is selected and pool is above move all threshold percentage:   86% > 60%.
=> Moving all files from cache_downloads to user0
find: ‘/mnt/cache_downloads/TV’: No such file or directory
find: ‘Shows’: No such file or directory
find: ‘UHD’: No such file or directory
Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-02-04T194215.list for TV Shows UHD

 

I wrote a comment on this thread explaining the fix, see attached.

 

 

I hope it may help someone in the future!

That one is known issue that also affected the stock mover in V7 and we were talking about it a few pages back, it has now been patched with P1.0.0 but this plugin hasn’t had an update for a few months now and needs a similar patch applied manually, as you laid out in your other post.

 

Thanks for posting the patch details though, very handy and I can confirm it works as I have tested it on my machine, though I don’t have any spaces in my share names.

 

I've always had an aversion to spaces in any file or folder names because issues like this seemed to always crop up and break things.

 

Edited February 5, 20251 yr by Faceman

On 2/5/2025 at 3:12 AM, DToX_ said:

Hi all, I found an issue where the mover would not move files for user shares that have spaces in the name.

Examples: "TV Shows", "TV Shows UHD", "Movies UHD"

Error Log:

 

I wrote a comment on this thread explaining the fix, see attached.

 

 

I hope it may help someone in the future!

On a slight tangent, have you figured out how to make changes to age_mover stick after reboots? I made my own code changes to fix ignore files but my file gets replaced on every reboot.

So I manually have to replace it at the moment (I can prob just automate via script if I get round to it). I've also tried replacing the age_mover file in the package file under /boot/config/plugins/ca.mover.tuning but that gets overwritten as well on reboot. So just wondered if there is a trick to it I'm not aware of. 

pretty sure it is configured to update on boot, so it would pull the file from github and replace your modified .txz every time.

So you could change the script in the .plg file to stop if from doing that, or even to pull from your own personal fork at boot.

 

Or you could have a small script that goes in and replaces the age_mover file after the fact, which is probably safe but remember to remove it if the plugin is properly updated again.

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

I switched to the "new" mover today because I realized the older one wasn't working anymore since I moved to unraid 7.  Here is my question because some options with size and date filters have changed:

 

1. I want to always move files older than 10 days... no matter what the % of the cache drive is full.  This option is either missing now or the first filter of:

 

2. Only move if above this threshold of used Primary (cache) space.  Why is it stated like this???

 

3. The old plugin had an option to run on size OR days.  This is what I want.  IF the size is over 75% run down to like 50% or something like that... and move the older files first.  BUT when it runs anything over 10 days is moved regardless of the % full.  I don't need anything over 10 days sitting on the cache drive.

 

Why was this in the old one but not the new one?  And if it does actually work like this "size OR days" then this needs to be more clear.  The first filter stated the way it is makes it sound like or is making it only run if its over a certain % full.  If this is the case and it doesn't even move older files anymore unless the % is met this needs to be changed back or at least the option to select OR.  

 

Thanks!

2 hours ago, slikone27 said:

Why was this in the old one but not the new one?

may as the author rewrite it completely and decided like this

 

and you are always free to use it or not, its a plugin written by someone in his free time, this is not a Unraid feature, its a extra plugin.

 

personally, this makes absolut sense to me as is, but it may doesnt fit your personal needs, so if you would like a feature and are not willing or able to write a plugin yourself, may rather ask if the author would implement the feature you would like to have ...

https://github.com/R3yn4ld/ca.mover.tuning/pull/69

If some one else can test will be cool ...

12 hours ago, alturismo said:

may as the author rewrite it completely and decided like this

 

and you are always free to use it or not, its a plugin written by someone in his free time, this is not a Unraid feature, its a extra plugin.

 

personally, this makes absolut sense to me as is, but it may doesnt fit your personal needs, so if you would like a feature and are not willing or able to write a plugin yourself, may rather ask if the author would implement the feature you would like to have ...

Apologies... That is what I was doing, it was just late lol... So is it indeed not working unless it goes over that % threshold?  Haven't had it installed long enough to see.  And could someone please add the "OR" option lol... For me I want to keep new shows etc on the cache drive for 10ish days (so people can watch them and they start quickly) and then after that time move them to the array regardless of the % full the disk is.  I like the % option as well incase I am grabbing large shows with lots of seasons etc and I want it to move stuff off when it gets full before it becomes completely full... Just really want the "Either/OR" so its whichever one comes first. @Squid

Edited February 7, 20251 yr by slikone27

5 minutes ago, slikone27 said:

So is it indeed not working unless it goes over that % threshold? 

 

yes

 

5 minutes ago, slikone27 said:

Just really want the "Either/OR" so its whichever one comes first.

 

should be pointed to @Reynald who is the current dev of this plugin

I doubt @Reynald is still active on the project, he hasn't given sign of life for more than a month, be it here or on Github. We might have to make yet another fork.

19 minutes ago, slikone27 said:

For me I want to keep new shows etc on the cache drive for 10ish days

 

Did you checked `Move files off Primary (cache) based on age` flag ?

10 minutes ago, foux said:

I doubt @Reynald is still active on the project, he hasn't given sign of life for more than a month, be it here or on Github. We might have to make yet another fork.

 

Well i posted pr based on @DToX_ changes for fix issue with spaces , i hope he will check/merge it ?!?

5 minutes ago, Masterwishx said:

 

Well i posted pr based on @DToX_ changes for fix issue with spaces , i hope he will check/merge it ?!?

We can only hope, but given his last message, it seems like he has moved on from Unraid to Truenas

 

 

3 minutes ago, foux said:

We can only hope, but given his last message, it seems like he has moved on from Unraid to Truenas

 

 

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 ...

19 hours ago, MrMatt said:

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

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.

4 hours ago, alturismo said:

 

yes

 

 

should be pointed to @Reynald who is the current dev of this plugin

 

4 hours ago, foux said:

I doubt @Reynald is still active on the project, he hasn't given sign of life for more than a month, be it here or on Github. We might have to make yet another fork.

well shit that all sucks lol... how does the days even work then?  If I have that selected does it have to be over the threshold and past the days?  That really seems crappy.  I really want to move if it goes over a percent so the disk doesn't fill up but keep anything under 10 days on so people can start the episode without waking disks.  to me that seems like the best use for this plugin and how i always used the old one.

 

if he isn't active anymore... is anyone planning on forking it?

This might be a silly question but is it possible to have multiple Ignore file and folder listed text paths.

For example If I have 

File list path: /mnt/user/system/plexcache/plexcache_mover_files_to_exclude.txt is there a way to add an additional path/.txt file for it to check through/ say  

 

File list path: /mnt/user/system/plexcache/plexcache_mover_files_to_exclude.txt, /other/path/to/file/ignore.txt 
Or some other formatting to achieve this? Thanks! 

Edited February 7, 20251 yr by Healzangels

4 hours ago, slikone27 said:

if he isn't active anymore... is anyone planning on forking it?

 

Created a fork here, adding the fix for empty file path from @DToX_ and includes another bug fix that I discovered where the sparseness setting does not work at all. Untested as I'm away from home atm, but if someone could test and open issues/PR's as appropriate I'd be happy to merge them.

 

I rewrote the packaging code to make it easier to bundle it into a Github action later so definitely let me know in case the latest plugin archive doesn't work.

On 1/5/2025 at 8:00 PM, Reynald said:

Sorry if I were away for too long.

 

I'm going to catch my backlog and restart maintenance and updates of this plugin next week 

Hi @Reynald, may a Info note if you are still considering to maintain this project ?

 

just before we may cut here and open new support Threads for forks.

 

Thanks ahead for a Info

11 hours ago, slikone27 said:

if he isn't active anymore... is anyone planning on forking it?

Already forked and made pr. waiting if no reponce will try compile and post new version ....

if the plugin should unmount and destroy zfs datasets ?

49 minutes ago, Masterwishx said:

if the plugin should unmount and destroy zfs datasets ?

i cant imagine this plugin will touch anything on the FS ...

 

simple rsync from a to b by rules

Hey, I wanted to use the setting "Move files that are greater than this many days old: Auto".

Unfortunately this will calculate share usage of shares that have no mover enabled. The shares are on their own single disk pool for a reason, but the mover still is trying to calculate share usage, and on this single disk shares it takes days to calculate share usage.

 

Is there a way to not take single disk shares with cache disabled into account for the calculations of the AUTO settings?

 

 

Feb  8 09:11:10 Tower move: Primary storage: storjone - size: 19TiB - used:  38 % (6.9TiB)
Feb  8 09:11:10 Tower move: Secondary storage: none
Feb  8 09:11:10 Tower move: Share Information: Name: storj1 - Path: /mnt/storjone/storj1
Feb  8 09:11:10 Tower move: Mover action: no action, only storjone used (cache:only).
Feb  8 09:11:10 Tower move: => Nothing will be moved. Share usage is taken into account in the calculation of the threshold for other shares.
Feb  8 09:11:10 Tower move: Calculating share usage... (can take a moment)

 

The second to last line is what I'm referring to. Nothing will be moved but the share usage calculation will take days (and there are more of such single disk shares that come after this one)

25 minutes ago, alturismo said:

i cant imagine this plugin will touch anything on the FS ...

 

simple rsync from a to b by rules

Yep, checked again can't find in code, but unraid mover has it, will try to add it to plugin...