That makes sense. Ive got 25Mbps up and an array of 8 drives so i dont ever get anywhere close to being limited by the drive speed when seeding, ive got to set the upload limit well under what a single 7200rpm drive can saturate. I manage to get lots of torrents up to a pretty high ratio and keep a good ratio on all my private trackers with a 1.5 MB/s upload limiter though, so maybe you could just turn your limiter to… lets call it 20MB/s? A 7200 rpm drive should be able to do atleast 80MB/s, so if you just set a reasonable limit you will still be able to seed out more than your fair share of data without messing up your viewing experience. Then you can put all your drives in one pool in the storage server and de-duplicate everything.

Unless you are just REALLY into having the high score on seeding ratio, i am not sure allowing qbittorrent to saturate your hard drive bandwidth is necessary, although as a member of the community i greatly appreciate your efforts to seed so much data!

If its running as a service on bare metal then the issue i described should not apply to you, as the files are all on the same harddrive as far as sonarr is concerned. I am by no means an expert on squashing config issues wrt this stuff, but there are people who know considerably more than me hanging out in the sonarr reddit who could probably help. Sorry to point your towards a corpo hell hole, but thats the place that I know where the people that actually know their shit and want to help are hanging out.

Yes that is absolutely something you can do. All you would need to do is set up a network share on the download box and then mount that share as a drive on the jellyfin box and then you should be able to do anything to it you would be able to do to folder sitting on its own hard drive. However, if you then use that to copy all the data to a second drive on the jellyfin system this leaves you hosting 2 copies of every file you want to see and manually renaming them over SSH or in a file explorer. But we can already access the download systems drives over the network right? So… Cant we just read all the data right off the download system over the network instead of storing two copies of it? You bet your ass we can…

What i would suggest is that you pick a single computer to be your storage system, and store ALL your data there. This will allow you to use sonarr to automatically create symlinks between the downloads and media folders, so that it can rename and organize your stuff for you without you doing anything, while also seeding the torrent in perpetuity and only using the data of a single copy of the file. For the same reason that you could use a network share to copy the data from the torrent box to the media server, you could also just use a network share to read all the data directly off a single storage box. At enterprise scale the storage is often an entirely seprate machine from the machine doing the compute, and the data all flows over network shares, allowing many compute servers to all access data from a single machine to prevent data duplication. I would strongly consider moving to a system where all your mass storage is centralized in one location, removing the need to duplicate production files across multiple machines (outside of the context of backups, which are a good thing). You can hook as many compute nodes as you want up to that single “Network attached storage” device and read the files off it to all those computers, none of which require more than a small ssd to run their os. This will give you twice as much storage on the storage node, becuase your not duplicating it on the jellyfin node.

All that being said, i am also going to assume your operating at a pretty small scale here and likely dont need very much compute, certainly not two computers worth. You should ABSOLUTELY be able to run jellyfin sonarr and qbittorrent off a single box that also acts as your NAS / central data storage location, without any performance issues, unless you have dozens of users or are transcoding like every single file your family is playing. On the jellyfin end, make sure you are set up to be direct playing the files at native resolution and not asking your server to trasncode them to another resolution, this uses lots of resources if you dont have a gpu or a intel cpu with quicksync. On the hardware side, what are you using? I run about 45 docker containers with no performance degradation and stream to up to 4 simultainous plex users WITH transcoding to lower the bitrate cuz my internet sucks and I do all that on a old 8th gen i5 i got out of the garbage. You should be able to get a used bussiness computer off ebay for 100 dollars that will run jellyfin and a sonarr stack with LOADS of overhead left, all on one device so you dont have to worry about network storage and getting bottlenecked by your networking equipment. If you tell me what it is running on i can maybe give you a better idea of if you have some kind of configuration issue, or its just antiquated hardware. But all this shit runs on a toaster. People use raspberry pis. I would imagine there is some kind of config issue leading to performance degradation.

Did you set the paths for your mounted folders in the docker appropriately? If you have the download folder and the media library mounted as distinct shares in the docker template it can break the links. I had to put the download and media library folders in the same mounted directory to make my links work.

I had /mnt/user/media/tv mounted to /tv And /mnt/user/media/downloads mounted to /downloads and had to change to so I just had /Mnt/user/media mounted to /media, with the download and media library folders both existing as subdirectories inside of /media to make them link properly. There is a faq on the sonarr reddit about this exact issue and it’s a common failure point.

Sonarr/radar will organize and rename the ones without torrents for you… Don’t do it manually. Just point them (sonarr/radarr) at the downloads folder as an import folder. Sonarr is for TV and radarr is for movies, if you didn’t know.

I was amazed when I found it this was how you were supposed to do it, and also kinda mad about there being no way for me to go back and seed the thousands of torrents I had renamed to get them to play right with Plex imports. Oh well, you live and you learn. If you have any issues the sonarr subreddit has some great guides in the sticky section and fairly helpful users that should be able to get the symlink think sorted out. Noone tells you that’s how it’s supposed to be when you start, you kinda have to bump into the information when you get mad about this very problem.

Good luck! I bet you’ll be pretty happy with the drastic reduction in labor once you set it up

Have you heard of our load and savior “Automatically renaming and organizing with sonarr and using symlinks to preserve the naming of the torrent downloads so you can seed without using twice as much storage”?

Sonarr makes a symlink from the torrent download folder to a new folder where it renames and reorganizes the file, but the pointer for that file and the file in the downloads folder point to the same file on your hdd so.you have two copies with different names but only one “file”. Now you have a perfectly organized media folder to feed into Plex while all of those files also live in your completed downloads folder with the original naming conventions. And it’s all automagic.