Hello everyone! 
I have a share called "media" which is configured to only store data on the array and not use my cache_ssd at all.
Today I saw that 130 GB of my SSD is used up. I checked what's on the ssd and it had a folder called media and inside were some files I recently downloaded/extracted with Sabnzbd. When I ran mover manually the files stayed on the ssd

I don't understand how they got there, like I said I configured the media share to not use the cache ssd and I definitely didn't copy those files there manually. 

Is it safe to copy them myself from disk to disk? I head that you should always copy from share to share, not from disk to disk

 

Disk to disk is safe, or you could add the array as a secondary storage, and tell the mover to go from array to cache.

12 minutes ago, psxmicha said:

I don't understand how they got there,

You probably have a container path mapped directly to /mnt/cache_ssd/whatever instead of /mnt/user/whatever, that will bypass any share settings.

 

disk to disk is fine, share to share is fine, it's mixing the 2 that isn't. 

This could also be caused by the behaviour mentioned in the Caution in this section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

1 hour ago, Kilrah said:

You probably have a container path mapped directly to /mnt/cache_ssd/whatever instead of /mnt/user/whatever

just checked every docker I have. They're all mapped correctly to /mnt/user/sharename 
I'll read what Itimpi mentioned and then copy these files myself, thanks