Hi all,

I know I am not the only person with this similar issue before in the past. But I have noticed on occasion that I spot the share hoard set to not use the cache, but files / folders exist on the cache drive to fix common problems from time to time show up. I move the files using the file manager plugin, and I am then sorted until the warning comes back up. I have checked mover is running. But it seems not to actually move files from cache to array for some reason. Even with increasing the mover frequency (not sure what the default value is) there is no difference.

Upon researching it seems as if I have messed up default shares as I have for example shares set as cache only or array online. I think the main reason was due to wanting to write files directly onto the array without going to the cache drive. But seams to have caused the issues to show up. I want to see what the defaults are for app data, community apps, domains, download, ISOs and system. Then how do I fix the important share that has all my stuff to go directly onto the array, but if any files go onto the cache, then the files will get moved onto the array. Many thanks for your help.

30 minutes ago, Goldmaster said:

Then how do I fix the important share that has all my stuff to go directly onto the array, but if any files go onto the cache, then the files will get moved onto the array

These are 2 incompatible requirements.    If the share is set to go directly to the array then any files for the share on a pool are ignored.   If set to be cached on a pool they cannot go directly and only go to the array when mover runs.   You have to pick which of these two behaviours you want.

12 hours ago, itimpi said:

If the share is set to go directly to the array then any files for the share on a pool are ignored.

Many thanks, so really I need to look into why files that are supposed to go directly onto the array are going onto the cache drive? I believe it may be due to using root share and moving files from cache only place to array directly only, but for "speed" the files are just moved about on the cache drive. So am I right that it may be better to have files set to cache then array? Originally it was to reduce wear and tear on the SSD as I'm not bothered by network speed.

I have set primary storage to be cache then secondary storage as array then mover action as array to storage. I will see how that goes but would like to know what the default settings are for mover and shares

Edited December 27, 20241 yr by Goldmaster

It sounds like you may be falling foul of the issue mentioned in the Caution in this section of the online documentation.   If that is the case then you are probably best setting the share up to be cached and files later moved to the array.