4 hours ago, Faceman said:

 

In that configuration, once a day at 8AM, it checks if the disk is >95% used, if yes it will move files older than 1 day, but only until it returns to the 95% threshold, so it wont move much unless the disk managed to get significantly higher than 95% in the time between scheduled runs. with a rule set like that I would be running hourly so the cache doesnt get a chance to overfill as it is checked more regularly.

 

so if it got to 97% it would move the oldest files, ignoring anything less than 1day old, until it got back to 95% then it waits for the next schedule.

 

I think the descriptions do need some updating, because the behaviour doesn’t quite match the wording.

 

if you want to clear out ALL files more than 1 day old you need to set the clear down number to 0% so it moves everything older than 1 day.

 

 

we really just need an option to prefer days old over percent

8 hours ago, DanielPT said:

Again i really dont understand this? Why is it so diffrent from the last mover plugin?

because there was a extra feature added ... which is very useful ...

 

before >> only run when treehold (fillrate from your cache) was upper lets say 50 % (whatever you have chosen) and move ...

change >> also only run when treehold (fillrate) was upper lets say 50 % but you set a 2nd value to stop moving !

 

before >> just move everything when limit was reached ...

later >> just move the "difference" to keep your other (most common newer) files still on cache

 

what is so hard to understand on this feature ? in your upper sample. 95 95 ... you will play ping pong and its not mentioned to be setup like this

 

WHEN > 95 % is reached >> start moving ...

WHEN < 95 % is reached >> stop moving ...

 

so a single file could start the mover and stop it again ...

 

what is a real usecase

 

WHEN > 90 % >> start moving (based on age as sample)

WHEN < 60 % >> stop moving

 

so ~ 30% (90 - 60) will then get moved from cache to array, the ~ 60 % will be kept on cache ... based on age of files ...

 

now, just set a low value in terms you want to move almost anything to the array always, like the 5 % ((yes, i know its 5 and not 0), but hey ... dont you have anything kept on cache like Dockers, Isos, Domain Images, ... which are easily already filling up those 5 % anyhow ? and set your start treehold also low like 10, 20, 30, ... whatever ... whenever you want the mover to start ...

 

 

Maybe some of these people should consider playing with your Simple Mover, rather than the full Mover Tuning, as it probably does what they need.

7 hours ago, stephenjcarr2804 said:

The files move to the array, but the empty folders are left on the cache. 

What said in log when mover run, or check log file

3 hours ago, slikone27 said:

can we integrate that please?

Old you mean 2023?

For users who has real issue with plugin:

Please open issue on github for I can follow it and will try to fix what I can. 

 

Also prs are welcome. 

 

Hope some one with better bash knowledge can maintain the plugin instead of me!!! 😁

 

But for some time I can do it.... 

On 2/14/2025 at 5:01 PM, Masterwishx said:

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

 

I just ran into this as well. My cache pool is ZFS (always has been) and with all those options ticked still leaves empty folders behind.

40 minutes ago, Sptz87 said:

My cache pool is ZFS (always has been) and with all those options ticked still leaves empty folders behind.

Do you mean parent dataset or regular folder. 

Try delete them all. And then reuse mover. Check syslog file or mover logs

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.

3 minutes ago, MrMatt said:

Additionally, the newer forks that work with unraid 7 don't support the same simple operation of the original.

 

Yep, I wrote about it befor, so we have : 2023,2024,2025 versions

Hey, thanks for stepping up and getting the plugin to run on 7.0

Unfortunately I got a big problem with this version of the plugin, which results in it being unusable in my setup.

 

For some reason it seems to want to calculate share usage for shares that don't matter at all. For me it's shares that each live on an individual single disk pool with no secondary storage, where I host a storj node each (millions if not billions of small files).

 

I would like an option or workaround to completely ignore such shares on their own pool with no secondary storage.

Something like: pool has only one share and the share has no secondary storage -> no need to calculate share usage

 

Because right now it's doing this:

 

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

 

The calculation of the share usage takes at least a couple of hours and if the disk is busy it was stalled for over a day before I had to stop the mover and run it without the plugin to not completely fill the cache drives.

 

Tried different things with the exclude list but it seems to always trying to calculate share usage before anything else.

52 minutes ago, MrMatt said:

the newer forks that work with unraid 7 don't support the same simple operation of the original.

I was also surprised a week or two ago when found we have two version of mover... 

1 hour ago, toyberg90 said:

I would like an option or workaround to completely ignore such shares on their own pool with no secondary storage.

Something like: pool has only one share and the share has no secondary storage -> no need to calculate share usage

I will check it

13 hours ago, toyberg90 said:

Something like: pool has only one share and the share has no secondary storage -> no need to calculate share usage

Will add it in new version 

On 2/17/2025 at 5:22 AM, alturismo said:

now, just set a low value in terms you want to move almost anything to the array always, like the 5 % ((yes, i know its 5 and not 0), but hey ... dont you have anything kept on cache like Dockers, Isos, Domain Images, ... which are easily already filling up those 5 % anyhow ? and set your start treehold also low like 10, 20, 30, ... whatever ... whenever you want the mover to start ...

 

 

I would like to ask if it is also possible to implement the option to set the percentage to 0 instead of 5? 😅

3 minutes ago, Redskyer said:

I would like to ask if it is also possible to implement the option to set the percentage to 0 instead of 5

I need to check it how it's working, I think you can use force all on shedule instead. 

Basically I wanted to fix some issues if I can that plugin have now befor adding changing... 

If I choose that option, the original mover is used and all other options (filters) will be ignored.

I just wanted to ask, no hurry. 🙂

26 minutes ago, Redskyer said:

If I choose that option, the original mover is used and all other options (filters) will be ignored.

I just wanted to ask, no hurry. 🙂

What? Force all option? 

Yes.

1 hour ago, Redskyer said:

If I choose that option, the original mover is used and all other options (filters) will be ignored.

I just wanted to ask, no hurry. 🙂

Will be added in new version

Cool, thanks. 😊

Maybe you @Masterwishx have an Idea/Skills to implemented a Process Bars for the actually Mover Status or you can support his implementation?

 

Here (the last Posts) talking about maybe Unraid 7.1/2.

 

1 hour ago, Revan335 said:

Here (the last Posts) talking about maybe Unraid 7.1/2.

Sorry it's above my skills and someone already working on it for add to unraid. 

My goal was just to fix some issues for this plugin until someone will catch it to maintain. And seems it has not few... 

On 2/17/2025 at 5:22 AM, alturismo said:

because there was a extra feature added ... which is very useful ...

 

before >> only run when treehold (fillrate from your cache) was upper lets say 50 % (whatever you have chosen) and move ...

change >> also only run when treehold (fillrate) was upper lets say 50 % but you set a 2nd value to stop moving !

 

before >> just move everything when limit was reached ...

later >> just move the "difference" to keep your other (most common newer) files still on cache

 

what is so hard to understand on this feature ? in your upper sample. 95 95 ... you will play ping pong and its not mentioned to be setup like this

 

WHEN > 95 % is reached >> start moving ...

WHEN < 95 % is reached >> stop moving ...

 

so a single file could start the mover and stop it again ...

 

what is a real usecase

 

WHEN > 90 % >> start moving (based on age as sample)

WHEN < 60 % >> stop moving

 

so ~ 30% (90 - 60) will then get moved from cache to array, the ~ 60 % will be kept on cache ... based on age of files ...

 

now, just set a low value in terms you want to move almost anything to the array always, like the 5 % ((yes, i know its 5 and not 0), but hey ... dont you have anything kept on cache like Dockers, Isos, Domain Images, ... which are easily already filling up those 5 % anyhow ? and set your start treehold also low like 10, 20, 30, ... whatever ... whenever you want the mover to start ...

 

 

Okay got it.

 

But i and outhers would like the option to just move on age. Nothing else. It worked perfect before.

58 minutes ago, DanielPT said:

But i and outhers would like the option to just move on age. Nothing else. It worked perfect before

If you set threshold to 0% and set age it's not working?