I’d recommend you use deluge’s ability to download to a temporary folder and move on completion to the mount. It won’t use any extra space compared to writing to vfs cache which is essentially trying to do the same thing.
Also if you’re trying to seed from the mount, be aware, if the mount itself disconnects/isn’t available to deluge for any given reason when it’s seeding actively deluge will mark the file as needing a force re-check, which on a remote mount takes a very long time.
There are complications with this. @spicypixel summarized well and also keep in mind that a rescan of the torrent will essentially download the entire data locally.
I don’t think I will ever do this. Cache is more optimized to run media in players that random access data. I don’t know exactly how the torrent client chunks data or if it reads the file in sequence. I doubt it does that which would make it a poor reader for cache.
and it works fine when i tell deluge to download into /mounted
but:
before deluge starts to download with full speed, first rclone is full allocating this allocation file in gdrive.
So if i want to download torrent 2GB, deluge allocates it on disk,
not downloading yet but waits,
rclone is uploading this 2GB preallocated file,
deluge starts to download
after something like 15minutes rclone updates preallocated 2GB file with correctly downloaded 2GB file.
What can i do to make rclone not upload this prealloacted file, only upload the one correctly downloaded after 15minutes?
I would instead tell deluge to move the data after it downloaded to the mount folder rather than tell it to download it directly there. I know it supports that cause I do it. I first download on a SSD to get the full speed and then deluge moves it to a extern HDD.