It seems when I invoke the mover to move data from the cache to the array, nothing actually happens. If I have 25GB on the cache and invoke the mover, there is no read/writes to the array and the 25 GB does not change. Is this something I should be concerned about?

Depends on what's on cache, enable the mover logging, run the mover and then post the diagnostics.

Ok, thanks. Here is the diagnostics.

phoenix-diagnostics-20221003-1043.zip

Mover logging is disabled.

23 minutes ago, JorgeB said:

enable the mover logging, run the mover and then post the diagnostics.

 

8 minutes ago, JorgeB said:

Mover logging is disabled.

 

That's odd, It says in settings that it is enabled. Here is a screenshot.

It's not, try toggling it then applying.

22 minutes ago, NexusZero99 said:

I have seem odd behavior from the mover too. When I add large vids or image data, (mostly vids) some of the files get stuck in the cache. It's always random files it selected. But I found if I pull from my backup and send just those files it will move them to the array.

Please start you own thread.

13 minutes ago, JorgeB said:

It's not, try toggling it then applying.

Ok, I disabled it, hit apply and then enabled it again. Is it on now?

phoenix-diagnostics-20221003-1127.zip

Now it's working, though not sure what files are these:

 

Oct  2 16:00:01 Phoenix root: mover: started
Oct  2 16:00:01 Phoenix  move: file: //..g/...
Oct  2 16:00:01 Phoenix  move: move_object: //..g/... File exists
Oct  2 16:00:01 Phoenix  move: file: //..g/...
Oct  2 16:00:01 Phoenix  move: move_object: //..g/... File exists
Oct  2 16:00:01 Phoenix root: mover: finished

 

Go to shares click on "compute all" and post a screenshot of the results, we are only interested in any shares that are using cache.

Here you go...

Here is a screenshot of what is currently on the cache...

8 minutes ago, Erich said:

screenshot of what is currently on the cache

Those shares (appdata, domains, system) are set to prefer cache, which means keep them on cache and if any are on the array, move them to cache.

 

And that is how you want those shares. You don't want them moved to the array.

 

If those shares are on the array, docker/VM performance will be impacted by slower array, and array disks can't spindown because these files are always open.

 

Ok, got it. I think the data that was there (movie files) was moved eventually. I just didn't expect those shares (appdata, domains, system) to require that much space.

 

Thank you. I really appreciate the help.

 

3 minutes ago, Erich said:

didn't expect those shares (appdata, domains, system) to require that much space.

Most of that is your docker.img, which is set to a reasonable size.

Good to know. Thanks.