On 5/9/2025 at 2:26 PM, csimpson said:

No, I have logging disabled.  I'll enable it and see what the message is when it happens again.  I was just curious if there was a way to ignore certain files or folders...  Even ignoring the Shared/.Recycle.Bin path would be helpful, I'm just not sure how to do it.

Check notification if log is disabled

On 5/9/2025 at 2:26 PM, csimpson said:

Even ignoring the Shared/.Recycle.Bin path would be helpful, I'm just not sure how to do it.

Do you fine now ?

On 5/10/2025 at 9:19 PM, slikone27 said:

This was working great

What unraid version 6.12? 

22 hours ago, b-riched said:

PlugIn V. 6.9.0-rc2

This is not plugin version... It's min unraid version of the plugin compatible with. 

On 5/9/2025 at 9:15 PM, Masterwishx said:

I think it's not possible yet. But you can check override for shares if not on same shares. Or open future request on github

What do you mean by "override"? Let me elaborate what i am trying to do:

 

/data/.usenet [do NOT move]

/data/media/movies/[moviename]/.plexmatch [move]

2 minutes ago, steve1977 said:

What do you mean by "override"? Let me elaborate what i am trying to do:

I meaned to override shares. So you can set different options for it. 

 

Is the sharename "data"? 

You can use ignore folders/files? 

If I can set to ignore /data/.Usenet folder, this should solve my issue. I’d like to move everything except this folder. I marked it hidden as I thought this was the easiest way to prevent it from being moved. If there’s an “exclude folder” option, this would make it even easier

1 minute ago, steve1977 said:

If I can set to ignore /data/.Usenet folder, this should solve my issue. I’d like to move everything except this folder. I marked it hidden as I thought this was the easiest way to prevent it from being moved. If there’s an “exclude folder” option, this would make it even easier

Now I got it, you want option to excudule folder/file from move all hidden file? 

4 minutes ago, steve1977 said:

hidden as I thought this was the easiest way to prevent it from being moved

Why not to use ignore list option? 

Didn’t know “ignore list”. This may be exactly what I’m looking for. It allows to define some folders that the moved ignores / doesn’t move?

Just now, steve1977 said:

This may be exactly what I’m looking for. It allows to define some folders that the moved ignores / doesn’t move?

Yep you can make file to ignore folders/files, just check help description of this option 

1 hour ago, Masterwishx said:

This is not plugin version... It's min unraid version of the plugin compatible with. 

Ah, ok, in this case the installed Version was 2025.05.04.

Just updated to 2025.05.17, switching to dry run mode and see what happens. 

Edited May 17, 20251 yr by b-riched

On 5/16/2025 at 12:44 PM, b-riched said:

Any hint on how to set this up properly?

 

Just play with options in test mode enabled, and see the logs , also read the help description of options its very easy to setup , also you have default setup just change to what you need. Then disable Test Mode

17 hours ago, Masterwishx said:

So it should move after 95% until 50%

Exactly, that's the idea. And it used to work flawlessly before. Might have to do with the update from 6.12.x to 7.x? Unfortunately i cannot say, when mover stopped working as intended.

Any ideas what I could check or do?

41 minutes ago, TerabyteTitan said:

Any ideas what I could check or do?

 

What Unraid version ? 

you can post debug.zip downloaded from Help menu

7 hours ago, Masterwishx said:

 

Just play with options in test mode enabled, and see the logs , also read the help description of options its very easy to setup , also you have default setup just change to what you need. Then disable Test Mode

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? 

Same question with the second (freeing) threshold: 

Freeing means

• moving files off the primary until this threshold is reached (i.e. should be lower than moving threshold + max file size)
  BUT syncing will take place anyway and threshold only applies to moving ops’s when reducing occupied disk space down to the freeing threshold? 

 

Remark: the term “prime up” does not directly translate into German and is somewhat confusing. I would offer myself assisting with an Addon Translation for the German language pack if you considered to launch one. 

 

FILL UP/PRIME UP TO THIS LEVEL OF USED PRIMARY (CACHE) SPACE
confuses me the most. 

• what does “cache:prefer” mean and where do I toggle this?
• Does this decide on the cache rate, i.e. how many files are copied to the cache when read from the array? 
• Or does this decide how many cached files remain in the cache after a scheduled mover run? And if so how is this different from the combination of the moving and freeing thresholds? 
• Is the value supposed to be lower or equal to the moving threshold?
• Is the value supposed to be lower or equal to the freeing threshold?
• Or is this value completely independent from the first two thresholds? 

I know that my questions may appear a bit picky. But I really do want to understand what happens here before I accidentally have my disks pump TB’s of data. 

Many thanks for your patience. 

13 minutes ago, b-riched said:

what does “cache:prefer” mean and where do I toggle this?

 

When share is array -> cache in share settings

16 minutes ago, b-riched said:

First: are my presumptions correct

 

Did you checked help description of options?

8 minutes ago, Masterwishx said:

 

Did you checked help description of options?

Yes sir, and I did try some alternative settings, looked at the logs, seemed to understand how it works and in real ops it didn’t. This is why I’m here. 

21 minutes ago, Masterwishx said:

 

When share is array -> cache in share settings

I see, so if the share is configured cache -> array I can ignore this setting? 

2 minutes ago, b-riched said:

I see, so if the share is configured cache -> array I can ignore this setting? 

 

Yep fillup is only for Array->Cache

9 minutes ago, b-riched said:

Yes sir, and I did try some alternative settings, looked at the logs, seemed to understand how it works and in real ops it didn’t. This is why I’m here. 

So what you wrote is most correct:

 

Moving threshold = move after this threshold. 

Freeing threshold = free upto this treshold (until pool size + file size > freeing) 

51 minutes ago, b-riched said:

Remark: the term “prime up” does not directly translate into German and is somewhat confusing. I would offer myself assisting with an Addon Translation for the German language pack if you considered to launch one. 

I will try to add languages in some new version

10 minutes ago, Masterwishx said:

 

Yep fillup is only for Array->Cache

Ok that lifts most of the fog.