I have read through the support topics and unfortunately everything i am reading says it is setup correctly. (Or so I think) I have been using unraid for a while but still consider myself just above novice as there is still a bunch to learn so please include details if you provide a response. I updated from 6.x.x to 7.1.4 a little while back and at the time didn't realize that my mover wasn't moving file till recently. Mover was working in 6.X version. I have never had the mover tuning plugin so that isn't a issue. Unfortunately I am here asking for help from the experts, as I can't seem to find where the issue lies as my cache drive fills up. I have attached diagnostics but happy to provide any other information needed. Thank you in advance for any help.

sisyphus-diagnostics-20250721-2138.zip

Please post the name of the share(s) you expect to be moved.

I am guessing that the share anonymized as m---a is the one you expect to be moved? However that is set up incorrectly for this as it only has primary storage set. Mover ignores shares that only have primary storage set. For that share to be moved you would need Primary Storage: cache, Secondary storage: array; Mover direction cache->array.

The another share that is not completely as you would expect is the 'system' one that has some files on disk1. For those files to be moved to the cache pool to improve performance you need to run Mover with both the Docker and VM services disabled as they keep files open on that share which stops them being moved.

The share anonymised as 's----g' is set to be written only to cache but has files on disk3. Again this is configured incorrectly to get its files moved to the cache. In this case you would need Primary Storage: cache, Secondary storage: array, mover direction array->cache.

Once you have all the files for a share you want only on the cache pool you can then (optionally) remove the secondary storage option as you no longer need to get Mover involved for those shares. Doing that would allow such share to run as 'Exclusive' shares (as long as you have enabled this under Settings->Global Share settings) which can improve performance for such shares by eliminating the Fuse overhead that is otherwise involved for User Shares.

13 hours ago, itimpi said:

I am guessing that the share anonymized as m---a is the one you expect to be moved? However that is set up incorrectly for this as it only has primary storage set. Mover ignores shares that only have primary storage set. For that share to be moved you would need Primary Storage: cache, Secondary storage: array; Mover direction cache->array.

The another share that is not completely as you would expect is the 'system' one that has some files on disk1. For those files to be moved to the cache pool to improve performance you need to run Mover with both the Docker and VM services disabled as they keep files open on that share which stops them being moved.

The share anonymised as 's----g' is set to be written only to cache but has files on disk3. Again this is configured incorrectly to get its files moved to the cache. In this case you would need Primary Storage: cache, Secondary storage: array, mover direction array->cache.

Once you have all the files for a share you want only on the cache pool you can then (optionally) remove the secondary storage option as you no longer need to get Mover involved for those shares. Doing that would allow such share to run as 'Exclusive' shares (as long as you have enabled this under Settings->Global Share settings) which can improve performance for such shares by eliminating the Fuse overhead that is otherwise involved for User Shares.

Thank you for your reply. Your assumption is correct on the main share I that I am concerned about (media). I will see if I can implement these changes after I get home from work.

Respectfully

15 hours ago, itimpi said:

I am guessing that the share anonymized as m---a is the one you expect to be moved? However that is set up incorrectly for this as it only has primary storage set. Mover ignores shares that only have primary storage set. For that share to be moved you would need Primary Storage: cache, Secondary storage: array; Mover direction cache->array.
It was already set as such. (No changes made) Set to allow fast transfer of files to server (NVME) then have mover move them to array.

15 hours ago, itimpi said:

The another share that is not completely as you would expect is the 'system' one that has some files on disk1. For those files to be moved to the cache pool to improve performance you need to run Mover with both the Docker and VM services disabled as they keep files open on that share which stops them being moved.
I turned off Docker and VMs and ran mover again. Here are my settings:

The share anonymised as 's----g' is set to be written only to cache but has files on disk3. Again this is configured incorrectly to get its files moved to the cache. In this case you would need Primary Storage: cache, Secondary storage: array, mover direction array->cache.
Settings changed here is current:

Once you have all the files for a share you want only on the cache pool you can then (optionally) remove the secondary storage option as you no longer need to get Mover involved for those shares. Doing that would allow such share to run as 'Exclusive' shares (as long as you have enabled this under Settings->Global Share settings) which can improve performance for such shares by eliminating the Fuse overhead that is otherwise involved for User Shares.
Once I get this running properly I will implement this. Thanks you.

18 hours ago, JorgeB said:

Please post the name of the share(s) you expect to be moved.

Really the main one I am concerned that will have 99.9% of data to be moved is the media folder. I am backing up my physical media and dropping it on my server.

Added inline comments and screenshots. New Diag attached. Mover still not moving files. (Even tried with VMs and Docker turned off) I emptied recycle bin so the size has gone down.

Respectfully

sisyphus-diagnostics-20250722-2113.zip

For the record. I also tried mover in safe mode to no avail.

It's a capitalization issue; delete /boot/config/shares/Media.cfg, then reapply the share settings for media.

21 hours ago, JorgeB said:

It's a capitalization issue; delete /boot/config/shares/Media.cfg, then reapply the share settings for media.

Feel kinda goofy about that... I cant tell you how many times I looked at that and my brain didn't actually catch it. Thank you sir.