I’m happy enough to seed til kingdom come, but I’m not aware of any facility that allows this with the 'Arrs.

Is there a way to continue seeding after download is completed, and also after the files have been moved and renamed to conform to whatever convention you have in place that the media players can pick up?

I currently have them continuing for 3x ratio in the downloads folder but that’s duplicating files for who knows how long, and I don’t have an enormous amount of space.

Can the torrent client be hooked back to the files under their new names, and can it be automated?

  • Melmi@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    27
    ·
    1 year ago

    Sonarr/Radarr can be set up to use hardlinks instead of copying files. That way the file will appear in both places but it will only take up the storage space a single time. I believe it’s one of the advanced options under media management.

      • Melmi@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        6
        ·
        edit-2
        1 year ago

        Given that it’s not enabled makes me think that they’ve got some sort of weird setup like network drives or separate mounts (Docker?) or gasp they’re running the *arrs on Windows.

        Well, that or they just didn’t notice that hardlinks were already working.

    • GVasco@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      1 year ago

      one caveat is the need for *rr apps to have direct access to the storage filesystem, and not connect through some filesharing protocol (smb, NFS, etc…) afaik. ISCSI might be good since it’s presented as an actual system drive, speculating.

        • GVasco@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          CIFS is SMB under a diferent name, and it might be that inside a share you can hardlink, but not across shares in the same filesystem.

            • GVasco@discuss.tchncs.de
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              It’s neither, it’s a limitation of SMB, if you have multiple shares set-up that mount to the root of the SMB share, you can’t hardlink accross them, but inside a single share in the root of the SMB share apparently it’s not an issue.

              • dustojnikhummer@lemmy.dbzer0.com
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 year ago

                Fun fact, just encountered this very issue myself lol. I hate the fact that I had to set up share per dataset, but it works and with smb enumeration they at least don’t show up for other users.

      • LufyCZ@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I have my arrs connected through SMB and hardlinks work fine.

        I’d guess it’s more about the underlying filesystem, I’ve got ext4.

        • GVasco@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Are you sharing the top folder holding both folders where you’re creating the hardlinks or are you creating individual shares for each folder?

          • LufyCZ@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            The former.

            You cannot hardlink across drives, and I’m guessing the OS might not know it’s one drive if you’ve got multiple shares.

        • GVasco@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Sure *are apps might not have a way of knowing but they are still limited by SMB’s limitations. If you’re sharing individual folders you simply can’t hardlink across them. But my bad for thinking SMB didn’t allow hardlink inside the same share mount point.