I have a question that may have been answered before but I wasn't able to find it

 

I have 2 shares, downloads and movies, both shares are using cache=yes using the same cache drive

 

I noticed that after a download it's completed and my torrent client starts the transfer to the movies share unraid phyisically transfer the file inside the cache drive intead of just

reasigning it to the new share without coping it, this it's kind of waste of ssd longevity

 

There it's an option to avoid coping the file?

 

Thanks

28 minutes ago, dvillaseca said:

torrent client starts the transfer to the movies share unraid phyisically transfer the file inside the cache drive intead of just

reasigning it to the new share without coping it

This sounds like your torrent client is copying the file from source to destination and then deleting the source, instead of just moving it.

 

What you are wanting to happen is actually what usually happens (and can be unwanted behavior) when a file is moved. The linux command for move and for rename is the same, mv, and often a file will be "renamed" to another path on the same disk instead of getting moved to another disk, sometimes in violation of any settings for the destination user share.

 

For example, if you move a file from a cache-yes share to a cache-no share, it will often just get "renamed" and end up on cache anyway (in a folder named for the cache-no share) despite the destination share being cache-no.

Thanks fro your response trurl,

 

i will move the files a custom bash script insted of using the qbitorrent move feature

 

Thanks