My torrent client downloads files to internal SSD. When I'm low on storage (often), I remove some torrents from qbittorrent and move files to external HDD. It means I can't seed them anymore.

I want to be able to seed HDD torrents periodically. What workflow can I employ? I can think of:

Use 2 different torrent clients. One with "external" torrents only. It will never be launched when external HDD is not plugged in, therefore old torrents will not be marked as "missing files" and will not require verification every now and then;
Use single torrent client which can accept CLI commands to start/stop specific torrents. Before detaching external HDD I will run a script to stop all external torrents. I will resume them back again only when HDD is accessible.

Any other ideas?

all 11 comments

sorted by: hot top controversial new old

[–] Romkslrqusz@lemmy.zip 8 points 13 hours ago (1 children)

You can just change the destination through the context menu, qbt will move them and continue seeding.

You could also use the categories function for this purpose.

[–] podbrushkin@mander.xyz 3 points 12 hours ago (1 children)

I can move, but next time when I will launch qbt without external HDD accessible, those torrents will gain error status "Files not found" and will require a long verification process. This is what I'm trying to avoid.

I will check how categories can help managing this, thx

[–] quediuspayu@lemmy.dbzer0.com 5 points 12 hours ago (1 children)

It happens to me every time I forget to mount the second drive, I just close qbittorrent mount the drive and start again, it does the regular check that does every time it launches and all good.

[–] podbrushkin@mander.xyz 2 points 12 hours ago (2 children)

"regular check" - do you mean verification? Verification takes a lot of time, verifying 10s of gigs will take a lot of time. What do you forget, stopping torrents?

[–] quediuspayu@lemmy.dbzer0.com 3 points 12 hours ago (1 children)

I mean the one it does every time it starts, when it looks if everything is where it thinks it is. At least when I start it the progress bars are white and the status says checking or something similar, it takes maybe 4-5 seconds.

I don't seed 24/7, I shut down the PC most of the time, and I don't have all the HDDs on auto mount, I have remember to mount them before starting qbittorrent or it wont find half of the files.

[–] podbrushkin@mander.xyz 3 points 11 hours ago (1 children)

Thank you for this clarification, I will try to exit qbit and launch it again when HDD is accessible. Maybe it will reset those error statuses. I think it didn't work some years ago (error status remained, had to start verification).

[–] quediuspayu@lemmy.dbzer0.com 3 points 10 hours ago* (last edited 8 hours ago)

Now I'm having doubts about it. I know for sure that with Transmission it worked that way, on second start all the torrents with missing files were paused. With qpittorrent, one hour ago, I was pretty sure I didn't need to unpause the torrents but now I'm affraid of missremembering something. As soon as I get home in a couple hours I'll test it to make sure.

Edit: confirmed, all torrents resume correctly without having to verify them.

[–] brickfrog@lemmy.dbzer0.com 2 points 12 hours ago* (last edited 12 hours ago) (1 children)

You don't need to but #1 could be a bit easier if you prefer multiple torrent clients/instances for organization. qBittorrent / Deluge can run multiple instances so you could have like qBittorrent "A" instance pointing to your internal SSD and qBittorrent "B" instance pointing to your external HDD. That's just a quick example but I'm sure Transmission and other torrent clients can do the same.

The only tricky bit with multiple torrent clients is that they'd each need their own incoming connection port if you intend to be fully connectable (port forwarded). That may not be feasible if you're using a VPN that only gives you 1 port forward but otherwise it's doable, depends on your setup.

[–] podbrushkin@mander.xyz 1 points 11 hours ago

Seems reasonable, I didn't thought about port conflict. But in this scenario not running both clients at the same time also is an acceptable solution.

[–] CmdrShepard49@sh.itjust.works 2 points 12 hours ago

#1 is probably the easiest solution outside of leaving your external drive connect all the time.