I have a tiny 16GB USB as a disk1 driver and that's it for the main array pool. The cache pool has two m.2's. I thought I set to use cache only for the shares but its not very straight forward to manage what is on the data disk (I have no idea) yet it has 9GB or so used now. How do I erase that content and make sure it's stored on the cache pool instead?

 

 

My shares look like this:

 

 

Looks like it's isos that are somehow mapped to the disk drive but the settings are the same for each share (use cache pool for new files/folders). Seems to have bugged out and flipped back somehow?

You should look at the Help for the Use Cache setting for a share.    The value Yes does not do what you seem to think as although data is initially written to the share that value means later move it the main array.  You almost certainly want it to be Only for your Use Case.

Yep, You need to select Only if you want data to stay Only on the Cache. 

like itimpi said. If you click on the text with your cursor it should provide you with a floating ? and give you a drop down help dialog so you can be more informed. 

 

Also if I recall if you select Only and then click on the Mover button it should move it back automatically. 

 

Just remember any other setting than Only will use your Cache as a temp spot before moving it to the array. Obviously if you choose NO it will bypass the Cache and go directly to the array, which of course isn't your objective here. 

When setting up a share, the cache part can be difficult to grasp at first.

 

There are two element that can help you :

1. the built in help, just clic on the text and the help will show up.

 

 

2. there is a specific field that describe how the mover will work with the setting that is selected

 

 

 

 

With those two thing to look at, you should be able to set up your share appropriately.

TL;DR Set all your shares to Cache:Prefer and run the Mover. When the Mover has finished you can optionally set them all to Cache:Only. This will fix your problem but read the other posts to understand why.

Stop the Docker and VM services in Settings before using the Mover though, the mover will not touch open files.

Wow - humbled by the quick and thorough support - thanks everyone!