First of all: Thank you @Masterwishx for your great effort! 

I have installed the new plugin version, but I have a problem - that on the other hand may not have anything to do with the plugin. 😄

 

For most shares everything works as desired and the data is moved correctly:

 

Primary storage: cache - size: 1.8TiB - used: 34 % (635GiB)
Secondary storage: data
move: Share Information: Name: backup - Path: /mnt/cache/backup
move: Moving threshold: 5% (90GiB) ; Freeing threshold: 5% (90GiB)
move: Mover action: cache->data (cache:yes). Pool is above moving threshold percentage:  34% >= 5%.
move: => Will smart move old files from cache to data. Nothing will be moved from data to cache
move: Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-02-13T085228.list for backup

 

But for one share I get this message:

 

move: Primary storage: data - size: 53TiB - used: 56 % (30TiB)
move: Secondary storage: cache
move: Share Information: Name: media - Path: /mnt/*/media
move: Moving threshold: 5% (2.7TiB) ; Freeing threshold: 5% (2.7TiB)
move: Mover action: cache->data (cache:prefer). Pool is above moving threshold percentage: 56% >= 5%.
move: => Will smart move newest files from cache to data until freeing threshold. Older files will be moved from data to cache.
move: find: '/mnt/*/media': No such file or directory
move: Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-02-13T085228.list for media

 

Why is the path “/mnt/*/media/” and how can I change that? The /*/ notation only appears in this share and I don't see any differences in the share configuration.
The mover obviously cannot work with this path specification ("No such file or directory").

Any Ideas? Thanks alot!

 

_______

Edit: Nevermind, switching primary and secondary storage does the trick.
The path ist now correct.
Still: Despite of recognising 83GB of data in the exclude list, no file is skipped when mover is active. 🤷‍♂️

 

Primary storage: cache - size: 1.8TiB - used: 35 % (660GiB)
move: Secondary storage: data
move: Share Information: Name: media - Path: /mnt/cache/media
move: Moving threshold: 5% (90GiB) ; Freeing threshold: 5% (90GiB)
move: Mover action: cache->data (cache:yes). Pool is above moving threshold percentage:  35% >= 5%.
move: => Will smart move old files from cache to data. Nothing will be moved from data to cache
move: Skipping Files from List. File size are taken into account in the calculation of the threshold
move: List Path: /mnt/user/system/plexcache/plexcache_mover_files_to_exclude.txt:
move:     Ignored files are using 83GiB
move: Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-02-13T131159.list for media

 

Edited February 13, 20251 yr by mcgerk

Thanks @Masterwishx I updated, moved over to your copy. I was also able to simply copy my .cfg's over from the old version (and update the version= string.) We'll see how it goes overnight.

Edited February 13, 20251 yr by Moniker_30

I currently have a big issue that I've never had before.

 

Basically it looks like Mover, right now moving about 600GB of media into the array and it's exhausting just a single disk to below the minimum free space set (150GB). This has never happened before...

 

I have 2 other disks with 300 GB each available and it's just not moving to those for some reason?

 

these are my share settings

 

2 hours ago, mcgerk said:

no file is skipped when mover is active

 

Do you mean files not skipped that they in list and they moved? it was same in previous versions?

Edited February 13, 20251 yr by Masterwishx

35 minutes ago, Sptz87 said:

I currently have a big issue that I've never had before.

 

Basically it looks like Mover, right now moving about 600GB of media into the array and it's exhausting just a single disk to below the minimum free space set (150GB). This has never happened before...

 

I have 2 other disks with 300 GB each available and it's just not moving to those for some reason?

 

these are my share settings

 

If you using my updated version? 

Please post mover tuning setting

For users who have issues with plugin:

Please post if you are using my updated version. 

In this new version for now updates:

 

1. Fix by @DToX_ for spaces in shares

2. Added Clear ZFS datasets

3. Format code (spaces etc) 

 

So the rest the code is same nothing was changed, also will try to add debug for more easy find issues... 

Edited February 13, 20251 yr by Masterwishx

1 hour ago, Masterwishx said:

 

Do you mean files not skipped that they in list and they moved? it was same in previous versions?

Yes, the Plugin lists the files to skip correctly but moves them anyway. This was the same in the previous version of the plugin.

 

As I understand now, the part of the plugin responsible for this wasn't changed for now - so that behavior makes perfect sense. 😉

 

However, I would be very happy if you could check the ignore list function. It doesn't seem to work (at least for me) anymore since Unraid V7 at the latest. Maybe the behavior is also zfs-related?

21 hours ago, Masterwishx said:

there is option days old

Ahh yes there is

 

Thanks!

 

But i cant disable the "Schedule" Like i could before

1 hour ago, mcgerk said:

However, I would be very happy if you could check the ignore list function. It doesn't seem to work (at least for me) anymore since Unraid V7 at the latest. Maybe the behavior is also zfs-related?

I will check it

1 hour ago, DanielPT said:

But i cant disable the "Schedule" Like i could before

If you mean unraid mover option, not sure of it working when mover turning is on and option of plugin use mover tuning on button is on 

the plugins first option is to disable the scheduler, which it does say "effectively disables the plugin" but you can still fire it off manually if the "Move Now button follows plug-in filters" is also selected.

 

The way the config page of the plug-in was made unfortunately hides all the options if you select that, which I don’t think it should (there is a lot of re-wording and settings changes I would make to clean up the settings and descriptions), but it still works when you click "move now" or if you call the mover manually by copying the "/usr/local/sbin/mover start |& logger -t move &" command into an external script or some other trigger.

Edited February 13, 20251 yr by Faceman

5 hours ago, Faceman said:

the plugins first option is to disable the scheduler, which it does say "effectively disables the plugin" but you can still fire it off manually if the "Move Now button follows plug-in filters" is also selected.

 

The way the config page of the plug-in was made unfortunately hides all the options if you select that, which I don’t think it should (there is a lot of re-wording and settings changes I would make to clean up the settings and descriptions), but it still works when you click "move now" or if you call the mover manually by copying the "/usr/local/sbin/mover start |& logger -t move &" command into an external script or some other trigger.

You are so right

 

It should not hide the options. Becurse i just wants it to move on age. I could do that before

 

Here is a screenshot from before

if you disable the schedule it will only work if you manually click the move button, that was the same on the old versions too.

 

There is no active file age checking going on, the script only runs when it is called and the only things that call it are the scheduler and the move now button?

 

Perhaps you are looking for the way to run it without thresholds set? the current plugin does have a minimum of 5% instead of 0% which might be annoying in some niche cases where you want it to run on a very small collection of files but I cant see that being an issue?

15 hours ago, Masterwishx said:

If you using my updated version? 

Please post mover tuning setting

 

Yes, with your version. I was using 2023 which didnt work at all in unraid 7 so I installed yours

 

5 hours ago, Sptz87 said:

Yes, with your version

Can you check maybe unraid mover without plugin if it work as expected to be sure if it plugin issue? 

After updating from 6.12.15 to 7.0.0, and porting over to @Masterwishx version, porting over my .cfg's (and updating version= string), my age-based settings successfully executed overnight. I have had no abnormalities.

Hi 

 

Having some issues with this. 

After the mover runs, I am left with empty folders on the cache drive. I have checked that the option to clean empty folders is set to Yes. 

 

Running 7.0.0. 

 

Is this a known issue since upgrading to 7?

 

Cheers

1 hour ago, stephenjcarr2804 said:

Hi 

 

Having some issues with this. 

After the mover runs, I am left with empty folders on the cache drive. I have checked that the option to clean empty folders is set to Yes. 

 

Running 7.0.0. 

 

Is this a known issue since upgrading to 7?

 

Cheers

No this should work, if you have zfs you need clean datasets option on

1 hour ago, stephenjcarr2804 said:

Running 7.0.0. 

Did you switch to ZFS with 7.0.0? Then maybe it's not empty folders, but empty datasets that are left behind. 

There is a new option “Clean empty ZFS datasets” for this purpose.

On 2/13/2025 at 5:32 PM, mcgerk said:

Maybe the behavior is also zfs-related?

No it's not, but seems it's not working trying to fix it. 

@DToX_ seems we have issues in code same as your fix, will be cool if you can check my prs in dev in github if it's need more fix

13 hours ago, Faceman said:

if you disable the schedule it will only work if you manually click the move button, that was the same on the old versions too.

 

There is no active file age checking going on, the script only runs when it is called and the only things that call it are the scheduler and the move now button?

 

Perhaps you are looking for the way to run it without thresholds set? the current plugin does have a minimum of 5% instead of 0% which might be annoying in some niche cases where you want it to run on a very small collection of files but I cant see that being an issue?

Im sorry i dont understand.

 

It worked perfect before.

 

It was set to "Disable mover running on schedule" and i just set the based on age?

 

So you think it didnt "respect" that before?

49 minutes ago, DanielPT said:

"Disable mover running on schedule

Without shedule mover will not run

Upgraded to 7 and the new plugin - works well, except I noticed only with directories (not files) Date Created (macOS over SMB) is reset to the time it was moved. 

 

Is that expected?

Maybe because I have Clean empty folders: No ?

 

Otherwise I'll investigate further.

Can someone explain this to me?

...

#1 (my installed)

#2

#3

 

...and no alarm or anything by Common Problems.

(please tag me if you reply)

7 hours ago, NLS said:

Can someone explain this to me?

If you read above thread last version of plugin has issues with spaces of shares and not working, so I made new version of plugin with fix and will try to fix other issues until author will back or other user want to maintain the plugin...