mv file from cache to share (that uses no cache) results in the file being moved to the cache creating a share on the cache.
Hi guys, I got a weird behaviour here and would like to know if this is a bug or I've done something wrong.
I have a share called movies. The share is configured to live only on the array (no cache). Config looks like this.
I have another share which lives only on the cache called tmp
I `ssh` to the nas and move a file from tmp to movies
mv /mnt/user/tmp/jdownloader/movie.mp4 /mnt/user/movies/.
The end result is that a folder m
This is a by-product of the way that the underlying Linux system implements move. It first tries to do a ‘rename’ if it thinks source and target are on the same Mount point and only if that fails does it do a copy/delete. In this case both appear to Linux to be under ‘mnt/user’, and so it tries rename which has worked and the file is left on the cache. In such a case you either need to have the target set to Use Cache=Yes so that mover later moves it to the array, or do an explicit copy