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?

top 11 comments

sorted by: hot top controversial new old

[–] catloaf@lemm.ee 12 points 1 month ago (1 children)

Check the arr config. There's a hard link checkbox.

[–] Grippler@feddit.dk 7 points 1 month ago* (last edited 1 month ago) (1 children)

If youre using docker just remember to make sure the storage volumes of the containers are the same path (not just physical drive) as the torrent clients, otherwise it can't hardlink and just defaults to copying. I have about 8tb of redundant data before I figured out why my drives were filling so fast, that I haven't gotten around to fixing

[–] merthyr1831@lemmy.ml 3 points 1 month ago (2 children)

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

[–] Grippler@feddit.dk 3 points 1 month ago* (last edited 1 month ago) (1 children)

Yup, *arrs actually warn you about that

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.

[–] dmention7@lemm.ee 1 points 1 month ago (1 children)

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...?

[–] Grippler@feddit.dk 2 points 1 month ago* (last edited 1 month ago) (1 children)

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:

${path_to_storage}:/downloads/torrents
${path_to_storage}:/media

Qbit:

${path_to_storage}:/downloads/torrents

But this will work

Radar:

${path_to_storage}:/downloads/torrents
${path_to_storage}:/downloads/media

Qbit:

${path_to_storage}:/downloads/torrents

[–] dmention7@lemm.ee 1 points 1 month ago

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!

[–] Chewy7324@discuss.tchncs.de 3 points 1 month ago

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.

[–] paris@lemmy.blahaj.zone 1 points 1 month ago

I use Docker for my setup and mistakenly had my qBittorrent download folder and my *arr media folders mounted as /downloads and /movies as opposed to /arr/downloads and /arr/movies

The *arr programs running inside their containers don't know that the two folders are actually on the same drive because it sees them as two separate mount points. Once I changed my *arr containers to mount my directories correctly, the hard linking worked as expected instead of copying files over. I then ran fclones and recovered over 700 GB of storage from deduplication.

[–] dracs@programming.dev 1 points 1 month ago (1 children)

How are you checking the size? Some tools will split file size based on the number of hard links. So a 10GB file may show as 5GB in folder A and the other 5GB in folder B.

Also, if you're using Docker. Its crucial that your downloads and media directories are listed as a single volume. If it's two volumes, it'll copy rather than hard link.

[–] merthyr1831@lemmy.ml 1 points 1 month ago

I have a feeling it may just be TrueNAS reporting it weirdly, or at least not in the way I expected.

I've just checked the file system in the console and the folders in question have multiple hard links when I run ls -la.

I think TrueNAS is just marking the qbt download dir's size as the full amount of the folders before they're hard linked. Either way it's recorded I'm sure it's not actually duplicating the data now! phew!

And yes I'm aware of the docker issues, whilst vague radarr/sonarr explained it pretty well