So.. I can't believe this is even a rabbit hole that I had to go down.

99/10 I find linux operates in a more "it just works" fashion, or at least, I can find some way of getting it to work.

But I have come up against one of the most baffling issues: Is it basically impossible to torrent directly to a network drive in linux?

I'm downloading a largish scientific torrent. Its ~1.5 tb. I consider that to be a big, but not really that big of a dataset.

And what I can-not fathom, is that for whatever reason, it seems practically impossible to torrent directly from my (user) machine to a network attached storage device.

Has any one else ever encountered this issue? This seems ridiculous to me and that I must be missing something very very obvious. But to get this to work, I ended up having to install a torrent client on my NAS and download it directly. Which is not my preferred way to do things.

Thoughts? Reactions? Have you encountered this issue yourself?

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 9 months ago* (1 child)

There's plenty of ways to make it happen. Odd that you're having an issue at all - does your torrent client just not like network mounts?

You can always use a symlink/hard link to the network device, then your client will only see a local path.

I've done this in Windows forever because unlike Linux, Windows apps have historically been picky about network shares (not all, but many, especially in the 90's). Linux stuff usually is a lot more flexible with paths, which is why I'm perplexed you're seeing this issue today.

What's your setup? Do you have a NAS? What network access does it use/are you using? Samba? NFS?

Some details about the setup will help us see where it's potentially going sideways

  • source
  • hideshow 1 child comment
  • [–] [S] 2 points 9 months ago

    There’s plenty of ways to make it happen. Odd that you’re having an issue at all - does your torrent client just not like network mounts?

    You can always use a symlink/hard link to the network device, then your client will only see a local path.

    This is exactly how I would have expected it to work. I've tried every client I could (qbTorrent, deluge, transmission, might have been a few more). I tried hard links, smb, yep. All of it. And the deeper I went the more of an issue it seemed to be. I genuinely can-not comprehend how a torrent client wouldn't just work with a network drive. I stopped trying to fix the issue because I'm now downloading the torrent using my NAS client (again, NOT my preferred approach. I don't want my NAS doing anything other than being a NAS).

  • source
  • parent