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!
And it’s good to use hard links.
Can someone explain why, and what to use them for?
It basically creates a second pointer to the same inode which makes file moves instant. So instead of copying the data to a new location and deleting it from the old it points to the existing inode immediately. You can’t do it across filesystems though so that’s why trash guides recommends using
/data/media/tvand/data/torrentsinstead of the/tvand/downloadspaths the lsio setup suggests since docker treats top level folders as different file systems.It’s mostly useful for torrents in my experience when you need to reseed stuff but also don’t want to point Jellyfin/Plex to a live downloads directory for security reasons.
Op cant because he’s using 2 different filesystems