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!
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.
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.
Wouldn’t symlinks essentially “copy” the file? I need it to be deleted, so it doesn’t fill up the drive
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:
In both cases, the only additional data used is the metadata used for the link itself. The contents of the file on disk are not copied.
That’s not something they natively support, it’s hard links or a copy.