i have two unraid server install one 240 ssd drive in both machine i setup my download-complete and incomplete folder to cache only but now my media folder are writing  to them also but in the share config i have it set to no cache

Set your media share to cache-yes, run mover, then set it back to cache-no. That should get all of its files back onto the array.

I can think of some ways that a cache-no share could get files on cache and then would continue to put them on cache since this would be consistent with other settings for the user share.

 

Here are 2 ways that a cache-no share could have files on cache:

 

1) The user share wasn't set to cache-no previously, so files for the share got written to cache. Then it was set to cache-no but without ever moving files from cache. A cache-no share isn't moved, so they would never get moved.

 

2) You move files from a share that is not cache-no (yes,only,prefer) to a share that is cache-no. Since the mount point for all user shares is /mnt/user, linux might take the easy way and move the files on the disk instead of moving them across disks, with the result that cache now has files from a cache-no share. You can keep this from happening by moving disk to disk or moving from cached user share at /mnt/user/source-share to the non-cached user share at /mnt/user0/destination-share.

 

After you have a cache-no user share that already has files on cache, there are some other things that might cause additional files for that share to be written to cache.

 

1) You update a file for a cache-no user share, but that file is already on cache. The file would be updated on cache.

2) Split level requires that a file be written to the same disk as other files it is grouped with, and those files are on cache.

 

I haven't really tested all of these, and there may be other scenarios. Be interested to see what some of the other gurus think.

2) You move files from a share that is not cache-no (yes,only,prefer) to a share that is cache-no. Since the mount point for all user shares is /mnt/user, linux might take the easy way and move the files on the disk instead of moving them across disks, with the result that cache now has files from a cache-no share. You can keep this from happening by moving disk to disk or moving from cached user share at /mnt/user/source-share to the non-cached user share at /mnt/user0/destination-share.

.

.

.

 

I haven't really tested all of these, and there may be other scenarios. Be interested to see what some of the other gurus think.

This only affects moves at the command line or if you happen to have a docker application set up with only /mnt/ mapped to /mnt.  Over the network it would never be an issue.