I like how this forum thread has actual thoughtful and objective commentary that all point to how bad this feature is.

I will look in to that

Yes, but hardlinking doesn’t work if the files aren’t on the same petition.

My downloads folder is on the main harddisk.
The files are moved to an external ssd.

You see, the problem is that radar and sonarr move my files into designated folders. That is a good thing, but it also makes it so that my download client can’t find it again to continue uploading.

I have now set it up so that I keep a copy in my downloads folder for a week, but I don’t have the space to permanently keep two copies of all my downloads.

It would be great if radarr could tell my download client where the file has moved to so that it can keep on seeding indefinitely.

You’re right. Hardlinks have to be on the same partition though. My “downloads” folder is on my internal harddrive and me sonarr folders are on an ssd. That’s why it didn’t work.

Docker is your friend.

I have reinstated my server last weekend with a single big docker-compse file. I made a mistake and just restarted the docker-compose and it was fixed.

To avoid having to mix/delete/rename files. Make a shared volume. So that your download client downloads to the same actual folder as where your sonarr puts it. But to be fair, sonarr does things like renaming, so that it often doesn’t work that way. I just ended up making a cron job that deletes files older than 7 days from my downloads folder every Sunday at midnight. Hopefully that’s enough time to get a decent share ratio, if not, tough luck.

If anyone has a better solution to keep your download client (qbittorrent for me) uploading after sonarr moved the file, tell me.

The German language part is a tough one. I’ve been looking for Dutch dubbed children cartoons, but I haven’t found anything yet.