Hi all,

the mover is not any files, no matter if I use the plugin or just the standard mover setting. Also when I manually trigger the "move" button, nothing happens.

 

SETUP

I have a rather uncommon setup in which I have a pool device that is the cache. I have another pool device (independent from the first one) that is my media library. New files should go to the cache first and then should be moved to the media library. The Array is for other data and does not have an upstream cache.

FYI: To achieve this setup, I had to use the new Unraid 7 version

 

URAID VERSION

7.0.0 beta 4

 

SHARE/MOVER SETTING

 

 

So the question is, what could be wrong here so that the mover is not doing its job. Is it only working with the Array? 

Something that I just realized: when I download new files, they are directly saved on the media_storage and don't even go to the cache anymore, which is exactly the opposite of what should happen

Thanks for any advice you can give me.

best regards

K

Edited December 14, 20241 yr by Kalypso

@itimpi >> 

from what I undeerstood from your message in August, my setup should work, right?

Remove the mover tuning plugin and retest.

21 hours ago, JorgeB said:

Remove the mover tuning plugin and retest.

@JorgeB thanks a lot, that seems to have done the job to actually move files. Is that a flaw in the mover plugin?

My Problem: My desired use case needs that plugin because I want to leave files as long as possible on the (nvme) cache (until it is about 80% full). But that is not possible with the standard built in mover. 

My plan B would be to move everything from the cache and then manually copy the currently used files back to the cache but that seems rather inconvenient

26 minutes ago, Kalypso said:

Is that a flaw in the mover plugin?

It's typical to be a problem, but don't know whether your case is a config problem or plugin bug, either way recommend posting in the existing plugin support thread to confirm.

On 12/15/2024 at 1:19 PM, JorgeB said:

It's typical to be a problem, but don't know whether your case is a config problem or plugin bug, either way recommend posting in the existing plugin support thread to confirm.

Thanks @JorgeB, I'll try that