Someone help me understand the sonarr to jellyfin workflow

[starvingmartist@sh.itjust.works]

So I've got jellyfin all set up, but I'm having some issues with files downloading from qbittorrent and Knowing exactly how and when they get moved over, either the sonar or jellyfin repository, whichever is the final destination. This is important because my torrenting drive is separate from my media drive. I have noticed some shows and files staying on my torrenting drive while others go over to the media drive. And I'm and to figure out where the issue might be that's causing this, I think I need a refresher on exactly how and when these files are supposed to be moved over. Since I can't find any sort of documentation inside the apps.

Can anybody explain this to me like super simply? I just took an edible and it's starting to kick in, but I still want to figure this out. Thanks y'all!

[lewdian69@lemmy.world]

I believe it's actual an interaction between Sonarr and qbittorrent and jellyfin isn't involved. Qbittorrent should have a setting for share ratio of when it's marked "complete". Like 1:1 download vs upload ratio. Then in Sonarr under the qbittorrent download client you check the box for remove completed downloads from the client. So popular together will reach whatever ratio you have set right away and be removed but others will take a long time or never hit that ratio.
Maybe, could have nothing to do with that and I have my concept wrong.

[starvingmartist@sh.itjust.works]

Uh oh, if that's the case I'm in trouble, see, I have a blanket "72 hours" seeding ratio set up in qbit, specifically for a private tracker I'm using, but the shows I download don't necessarily need that requirement.

I may have to find a way to only send seeding goals for specific torrents if seeding is causing it to not be transferred over

[deello@lemm.ee]

You didn't specify but this sounds like an issue where you are confusing sonarr and radarr where only one is configured "properly".

[plantsmakemehappy@lemmy.world]

If the torrents are still seeding when the import in arrs happens, it would copy the file(s) to your media folder so you'd have two copies now. If the torrent is done seeding and, I think if you have completed download handling enabled, it'll do a move instead so you'd end up with only one copy.

Ideally though you want a hardlink compatible setup but from what you said you do not.

Jellyfin just monitors your media folder which is managed by the arrs.

[starvingmartist@sh.itjust.works]

You're right, radarr is the one that handles moving stuff around isn't it? Tbh I've got massive add so I get super into these projects and the setup, but when it comes to maintaining, I've completely forgotten how everything works.

Would you happen to know how I can fix this through radarr?

[deello@lemm.ee]

Sonarr is TV and radarr is movies.

[lewdian69@lemmy.world]

But also, if you are just seeing the files on your drive but the torrents aren't listed in qbit anymore make sure to ignore me altogether!

[ragebutt@lemmy.dbzer0.com]

Do you have sonarr set to copy or hard link on import

Copy will fuck over your ability to seed, hard link will result in the files staying on your torrenting drive

[dan@upvote.au]

You can't hard link across drives, so it's not possible to use hard links if the OP wants torrents and media to be on two separate drives.

[hedgehog@ttrpg.network]

Is there a way to use symlinks instead? I’d think it would be possible, even with Docker - it would just require the torrent directory to be mounted read-only in the same location in every Docker container that had symlinks to files on it.

[ragebutt@lemmy.dbzer0.com]

Oh right duh. Disregard what I said, obviously. Been ages since I’ve used a setup that’s not one big pool

[starvingmartist@sh.itjust.works]

Oh yeah no I'm taking about sonarr then

[inverseparallax@lemmy.world]

That's not something they natively support, it's hard links or a copy.

[muntedcrocodile@lemm.ee]

U can always just use the media stack docker image it practically does everything for you

[couch1potato@lemmy.dbzer0.com]

If you're using docker it's easy to set up a second qbittorrent on a different port to meet different needs.

[evotech@lemmy.world]

Sonarr gets torrents and sends to qbittorrent, qbittorrent downloads the torrent and puts the downloaded file somewhere, sonarr then picks up that file and moves it to its final destination where jellyfin expects it

[starvingmartist@sh.itjust.works]

Wouldn't symlinks essentially "copy" the file? I need it to be deleted, so it doesn't fill up the drive

[felbane@lemmy.world]

No. Symlinks and hardlinks are two approaches to creating a "pointer to a file." They are quite different in implementation, but at the high level:

• Symlinks can point to other filesystems, hardlinks only work on the same filesystem.
• You can delete the target of a symlink (or even create one that points at nothing), but a hardlink always points to a real file.

[damage@feddit.it]

So, sonarr starts the download in qbittorrent, monitors it, and imports it in its Library once it's completed. First of all check inside Sonarr whether it has imported the file or not, it could be that it was imported but not moved.