6 hours ago, dohnutt said:

Hi there. I know the icon is already changed but if you want to keep the same icon as before but have a differentiator, you could use this which I just made based on the original

If users think this will be better I can change it

Just for info: two old versions was depricated... 

I'll say that I prefer the image that dohnutt created over the one that is currently in place. It's simple, as well that image is known to be used for the mover tuning plugin.

8 hours ago, Masterwishx said:

Just for info: two old versions was depricated... 

In that case it is probably better to just revert to the previous version in my opinion

4 hours ago, dohnutt said:

In that case it is probably better to just revert to the previous version in my opinion

Yep. Sure. The old image is cool and known to users howere is 7 years old image. If more users will ask for old icon I will change it. 

 

But in my opinion icon not so big problem for plugin as it has some issues that need to be fixed. 

 

Also if will have time for it I will try to add option to use unraid mover instead rsync but then some futures maybe will be disabled. 

I have an issue with the latest version. It started to move files from a prefer cache share to the array for no reason since the update.

Here is my configuration:

 

For example with my nextcloud share i see this in the logs:
 

07:16:19.764 Primary storage: cache_protected - size: 900GiB - used: 34 % (321GiB)
07:16:19.765 Secondary storage: user0
07:16:19.770 Share Information: Name: nextcloud - Path: /mnt/*/nextcloud
07:16:19.774 Moving threshold: 0% (0B) ; Freeing threshold: 0% (0B)
07:16:19.775 Mover action: user0->cache_protected (cache:prefer). Pool is above moving threshold percentage: 34% >= 0%.
07:16:19.776 => Will smart move newest files from user0 to cache_protected until freeing threshold. Older files will be moved from cache_protected to user0.
07:18:09.791 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-03-03T071617.list for nextcloud
07:18:10.746 ************************************************************ ANALYSING MOVING ACTIONS ***********************************************************
07:18:10.792 Deciding the action (move/sync/keep) for each file. There are 247573 files, it can take a while...
07:22:42.868 A total of 247569 files representing 325GiB will be moved/synced:
07:22:42.871 - 247569 files representing 325GiB will be moved/sync from cache_protected to secondary
07:22:42.876 *********************************************************** LET THE MOVING SHOW BEGIN ! *********************************************************
07:22:43.855 Moving "/mnt/cache_protected/./nextcloud/appdata_ocua1beakw9a/richdocuments/remoteData/discovery"  to  /mnt/user0/ 
07:22:57.214 247568 files remaining from caches to array  325GiB
07:22:57.251 Moving "/mnt/cache_protected/./nextcloud/appdata_ocua1beakw9a/richdocuments/remoteData/capabilities"  to  /mnt/user0/ 
07:22:57.362 Deleting empty dir /mnt/cache_protected/nextcloud/appdata_ocua1beakw9a/richdocuments/remoteData
07:23:05.138 247567 files remaining from caches to array  325GiB

It should not move it. The share is set like this:

31 minutes ago, JonasH said:

I have an issue with the latest version.

It was fixed in last version for prefer or unnanttend and rebalanced. For /mnt/*/sharename, it's not worked befor. 

13 minutes ago, Masterwishx said:

It was fixed in last version for prefer or unnanttend and rebalanced. For /mnt/*/sharename, it's not worked befor. 

I'm not sure if I understand this correctly. I actually just want the standard behavior of the mover as it was before and how it behaves with the mover from Unraid. What do I have to set so that the files remain in the cache as they should with a Cache Prefer share?

6 minutes ago, JonasH said:

I'm not sure if I understand this correctly. I actually just want the standard behavior of the mover as it was before and how it behaves with the mover from Unraid. What do I have to set so that the files remain in the cache as they should with a Cache Prefer share?

Please open issue in github I will check maybe some bug, what I meaned befor function for prefer or unnanttend and rebalanced not worked but maybe it's not correct for prefer like in your case

On 3/1/2025 at 7:37 PM, Masterwishx said:

Maybe you know how to fix issue for @foux with more than 100 files in igone list?

I can try have a look if I get a chance this week. 

On 3/1/2025 at 7:33 PM, Masterwishx said:

Thanks i will check it

Does it all make sense?   Would you like me to put up a PR on GitHub?

1 hour ago, JayBriers said:

Would you like me to put up a PR on GitHub?

Any prs are welcome, I think it should write to file maybe and then add it to filter list? @foux if it long ignore list. 

4 hours ago, JonasH said:

as it was before

How it was? cache Prefer of Unraid should move from array to cache.

 

Here I see from log : new files move to cache from array, old from cache to array. It's how should work in plugin? 

I'm running into an issue here, which I think has to do with "smart caching".

 

I have several shares set as primary cache, secondary array. 

Mover action is to move from array to cache (ie, to keep on the cache as much as possible, and only overflow to array if cache is full)

 

However, all of these shares now have their data on the array, because there are other shares that are set to flush to array, but only after a long time.

 

The expected behaviour here would be for the shares where cache is perferred to always be there, not to be moved out for other data.

(Yes, cache-only could be used, but in that case writes will fail in the event of cache being full, rather than succeeding to the array)

 

Let me know if anything is unclear from the above.

Settings attached.

 

Edited March 3, 20251 yr by -Daedalus

2 hours ago, Masterwishx said:

Here I see from log : new files move to cache from array, old from cache to array. It's how should work in plugin? 

its the worthest setting ever in Shares

 

cache prefer or cache < array ... keep files on cache until cache is full, then move to array, when free again, move back ...

 

i always suggest either cache only (promary only) oder cache > array (move to array) with plugin rules.

 

with the plugin rules AND the prefer rule ... it seems a hit or miss if that works or not

I'm trying to disable the "successfully moved files" notices.  I see an option in the scheduler to set it to "Errors only" but there is no submit/save button.  When I change it and then navigate away, and then navigate back it always resets to "Yes".  What do I need to do to save this notification update?

 

Sorry if its been answered a million times. I couldn't find anything with search.

Quote

3 minutes ago, orkim said:

I'm trying to disable the "successfully moved files" notices.  I see an option in the scheduler to set it to "Errors only" but there is no submit/save button.  When I change it and then navigate away, and then navigate back it always resets to "Yes".  What do I need to do to save this notification update?

 

Sorry if its been answered a million times. I couldn't find anything with search.

 

Apologies. It was my script blocker that was blocking the button from updating to the "apply" state.  I forgot to whitelist my unraid box after an update.  Please disregard!

I had the same issue last night, my cache_work <- array, moved everything to the array.

I just manually kicked the mover (click move button on main page, with no settings changes and everything moved back.

I do have 
Only move if above this threshold of used Primary (cache) space
and

Free down/prime up to this level of used Primary (cache) space:
set to 0 (zero), I assume these are the defaults when updating for unraid 7.

But that wouldn't explain why the files moved back?

1 hour ago, orkim said:

 

 

3 hours ago, -Daedalus said:

The expected behaviour here would be for the shares where cache is perferred to always be there, not to be moved out for other data.

If you mean issue with cache prefer it was fixed issue that not worked befor, please open issue on github and include logs and debug. 

As I added in last version validation of filenames for security checks, thanks to @AEnterprise for raised issue will add option in next version to enable/disable this check. 

Edited March 3, 20251 yr by Masterwishx

Can you post a link to the github? There isn't anything on the first post, and I'm not 100% sure which mover plugin is yours from CA.

17 minutes ago, -Daedalus said:

mover plugin is yours from CA.

It's only one now

19 minutes ago, -Daedalus said:

mover plugin is yours from CA.

It's only one now

https://github.com/masterwishx/ca.mover.tuning

I had the same thing happen last night. I updated to the new version for unraid 7 a week or so ago. Last night my cache_work <- array share put all the files in the array.

I have the settings 
Only move if above this threshold of used Primary (cache) space:
and
Free down/prime up to this level of used Primary (cache) space:
both set to 0% (I assume the default when I did the update).

I just manually kicked off the mover via the Main page, and the files moved back.

20 minutes ago, -Daedalus said:

not 100% sure which mover plugin is yours from CA

What version of plugin you have?