4 minutes ago, Grobalt said:

but large files need to be moved to array

It will move after 95 % of cache pool

okay, until then i have no parity protection .. that is not the intention :D large files should be threshold independant .. always on array

will this work as temporary workaround ? i still have issues understanding the 3 thresholds ... best would be without tresholds

Edited July 31, 2025Jul 31 by Grobalt

Agreed, in the case of configuring syncing and moving based on file size there should not be thresholds. That would lower complexity. The total available space as well as the minimum free space are managed from upstream unraid share configuration.

18 hours ago, Grobalt said:

still have issues understanding the 3 thresholds

You can read in option descriprion:

Primary->Secondary (cache:yes)

Moving threshold : move after this

Freeing threshold : move until this

Secondary - Primary (cache:prefer)

Fill up threshold : move until this

okay, seems sync will never work as i would like to do .. so maybe a new plugin is needed. i am not able to code myself .. but i have no issue paying a few dollars for development

8 minutes ago, Grobalt said:

okay, seems sync will never work as i would like to do

Sorry to hear, if playing with thresholds not helping...

I'm just trying to fix past issues and added some futures users/I'm wanted with my ability, and most importantly not break already working stuff.

using these settings

maybe i achieved what i tried to achieve

37 minutes ago, Grobalt said:

maybe i achieved what i tried to achieve

Good, glad to hear that it was not in vain that I spent time by adding options and changing the code to make sync more flexible and useful to users :)

yeah, now figuring out how to copy thousands of jpg to cache in the correct folder structure :D

42 minutes ago, Grobalt said:

maybe i achieved what i tried to achieve

Also added sync for share override if you need different setting for shares.

The option clean empty folders is not working:

Aug  1 18:18:43 Unraid move: Deleting empty folder /mnt/cache/filme/Donnie Darko (2001) 2160p
Aug  1 18:18:43 Unraid move: rmdir: failed to remove '/mnt/cache/filme/Donnie Darko (2001) 2160p': No such file or directory

15 hours ago, Grobalt said:

The option clean empty folders is not working:

Folder not exist?

17 hours ago, Grobalt said:

The option clean empty folders is not working:

It's just visual issue Becouse folder already moved, will be fixed in next version

ok, because it was for every folder :D

i had to delete some stuff today .. it deletes the files from cache but if they are synced to array, it will not touch array files :( so i have to delete them twice unter /mnt/user ... ok, it was worth a try, but like this it is not usable with "sync"

11 hours ago, Grobalt said:

ok, it was worth a try, but like this it is not usable with "sync"

This is how unraid works

@Masterwishx

Can this helper text be updated for clarity? A standard format could be

" Setting to Yes effectively disables the plugin schedule"

Specifically for the test (dry run) mode; the current help text makes it sound like setting to No would disable the plugin but that's counterintuitive to what "Test Mode: No" reads as

30 minutes ago, Shu said:

like setting to No would disable the plugin but that's counterintuitive to what "Test Mode: No" reads as

Sure I can update it but you refer to two options that have separare help texts.

In test mode help text refer to another option that if it set to No.

Anyway will try to update it

Edited August 10, 2025Aug 10 by Masterwishx

On 8/10/2025 at 10:01 AM, Masterwishx said:

Sure I can update it but you refer to two options that have separare help texts.

In test mode help text refer to another option that if it set to No.

Anyway will try to update it

Yes, sorry for the confusion. If it's helpful, here's what I'd put forth:

1. Disable Mover running on a schedule - "Setting to Yes disables Mover from running automatically"

2. Test Mode (dry run): - "Setting to Yes enables Test Mode"

3. Validate input filenames to prevent attacks - "Setting to No disables validation of filenames"

Feel free to copy, modify, or ignore. Thank you, @Masterwishx!

On 8/12/2025 at 5:50 AM, Shu said:

Yes, sorry for the confusion. If it's helpful, here's what I'd put forth:

1. Disable Mover running on a schedule - "Setting to Yes disables Mover from running automatically"

2. Test Mode (dry run): - "Setting to Yes enables Test Mode"

3. Validate input filenames to prevent attacks - "Setting to No disables validation of filenames"

Feel free to copy, modify, or ignore. Thank you, @Masterwishx!

Ohh you mean help from the right, I was thinking we are talking about help text inside, when click on option :)

21 hours ago, Masterwishx said:

Ohh you mean help from the right, I was thinking we are talking about help text inside, when click on option :)

Yes, sorry haha - the next alongside the setting; not the popup description inside

28 minutes ago, Shu said:

Yes, sorry haha - the next alongside the setting; not the popup description inside

I will try to change help description inside but, description from right is not clear?

I think I've got things understood here with the synchronization setting. Would anyone mind double checking my understanding? I'm effectively trying to create a Least Recently Used cache for my array. Where the most recent files (by the date they are written to the server) are kept in cache and are written to the array for parity protection.

The goal is to avoid spinning up array disks unless:

1. parity is being checked

2. the user would like to access a very old file.

I believe this is what's happening with the "Synchronize Primary files to Secondary" setting. I've made a visual for this below going through 5 sequential steps.

2 hours ago, tooApe said:

I think I've got things understood here with the synchronization setting.

You need to read help description of options by click on it.

And please read this and maybe some pages back about how synchronise work.

Edited August 16, 2025Aug 16 by Masterwishx

I have read the option description and have been through this thread a few times but some of the conversations about it are a bit confusing. This is one of the better outlines of the behavior that I found:

On 5/17/2025 at 10:25 AM, b-riched said:

Well, when it comes to data I believe “trail & error” is not exactly the right approach.  Especially considering that the tuned mover does not seem to show the same behavior in dry-run and in real op’s. So maybe we could leave the RTFM mode and come to some more decent questiens. 

 

First: are my presumptions correct? 

1. “move” means copy from source to destination + delete from destination

2. “Synchronize” means copy if newer than the same files at destination + not delete from source. Toggling 
   PRIMARY FILES TO SECONDARY to YES
   leads to every “moving” operation to stay as described (if files are new) apart from files not being deleted from source. 

3. “Synchronize “ means syncing from source to destination and NOT also syncing from destination to source.

Given that these presumptions apply

   ONLY MOVE (sync) IF ABOVE THIS THRESHOLD OF USED PRIMARY SPACE 

(moving threshold) means 

• no moving will happen if cache fill level is not reached? 
  AND no syncing will happen likewise? 
  OR (presumingly) 

• no moving will happen if cache fill level is not reached? 
  BUT syncing will happen anyway? 

There wasn't much confirmation that this was the correct understanding of "synchronize" works.