I ask this because whilst *arr apps supposedly import downloaded torrents to their respective media folders, my downloads folder for qbittorrent is over 200GB in size when I’ve got zero incomplete downloads.
Have I set something up wrong? Or is it setting some kind of hard link between the downloads and media folder?
Yup, *arrs actually warn you about that so I fixed it before I started downloading anything.
Hardlinks aren’t a big issue for me but does explain how I had a bunch of “deleted” items in my plex folder when I migrated recently - I must have only deleted the qbittorrent (or plex) inode and left the other to get imported
qbit_manage has a feature where it’ll check whether a hard link exists outside of the torrent directory, and deletes the torrent if it’s only in the (qbit-)torrent directory.
This would’ve automatically removed the torrent once you’ve deleted the files from *arr. I recommend against deleting files from Plex, as *arr could detect them missing and redownload them.
Yeah they’re just fairly vague about what you need to do for hard linking to work IMO. I just had the same shared folder that all containers pointed towards for their data directory, but since the directory inside the qbit and *arr containers didn’t have the exact same name and path, hard linking didn’t work.
Wait can you expand on that a little more? I literally was just now getting ready to try and troubleshoot why my hardlinking was not working.
I was under the impression that the torrent storage and media library just needed to be in the same share, but maybe there is more to it…?
The path inside the containers to where you download your torrents, so the path after the “:”, has to be exactly the same on both your torrent container and your *arr containers
Example below won’t work with hard linking
Radar:
Qbit:
But this will work
Radar:
Qbit:
Thanks I will double check that later. Reading the Trashguides, I didn’t catch that the paths had to be that identical.
It’s more than a little annoying that Radarr doesn’t throw any indication that it’s physically duplicating files rather than creating hardlinks!