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?

  • Grippler@feddit.dk
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    17 hours ago

    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
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 hours ago

      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
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        6 hours ago

        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