Don't uncheck "Use another path for incomplete torrent" on already-queued but unstarted torrents #16781

New issue

Open

opened 2026-02-22 03:24:43 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-22 03:24:43 -05:00

Owner

Originally created by @badhorsey on GitHub (Apr 14, 2025).

qBittorrent & operating system versions

qB 5.0.4 64-bit
OS Windows 10 pro 21H2
Qt 6.7.3
Libtorrent 1.2.19.0

What is the problem?

I've been downloading torrents to a temp drive, then moving to another drive when finished, to defragment them.
This causes lots of downtime 'coz you can't download to a temp drive and copy from that drive to the destination drive at the same time.

So I tried checking "Download parts in sequential order", unchecking "Use another path for incomplete torrent" so they'd download to the destination drive, and downloading just 1 file at a time, to see how much fragmentation I'd get. I did this en masse to dozens of queued downloads that hadn't been started.

I found my destination drive was filling up twice as fast as it should, without downloading any more files than expected. What happened was that when I unchecked "Use another path for incomplete torrent" for a torrent that hadn't started downloading yet, qB "moved" it to the destination drive (no actual moving involved, cuz they hadn't started), then CHECKED THE BOX AGAIN and changed the path for incomplete torrent to be the same as the path for "Save at".

I noticed this, and tried again to uncheck the "Use another path for incomplete torrent" for these torrents, since it now pointed to exactly the same directory as "Save at". But every time I unchecked it and then clicked "OK", and I immediately re-opened the torrent options window, I saw it had checked it and changed the incomplete directory again. I tried changing the incomplete path to a different directory, clicking "OK", opening the torrent options window again, seeing that it had done that correctly, then unchecking the box, clicking "OK", and opening the torrent options window again. The box had always been unchecked again and the incomplete torrent directory changed to match the final Save At directory.

So I just let it run, figuring it would just leave the downloaded torrent files where they were when it was done.

Yes it did, but...

After downloading each complete .!qB file in the directory for incomplete torrents, it copied it to the "Save at" directory without the .!qB torrent, without noticing that the destination directory WAS THE SAME DIRECTORY, and without deleteing the .!qB file.

So I ended up with two complete copies of each downloaded file in the destination directory, one ending in ".!qB" and one not.

Steps to reproduce

See above.

Additional context

No response

Log(s) & preferences file(s)

I couldn't find which log file contains relevant information, because my log files filled up with 300,000 lines like this: "(I) 2025-04-14T03:04:16 - Performance alert: 1499000: performance warning: max outstanding piece requests reached. More info: https://libtorrent.org/reference-Alerts.html#enum-performance-warning-t"

Originally created by @badhorsey on GitHub (Apr 14, 2025). ### qBittorrent & operating system versions qB 5.0.4 64-bit OS Windows 10 pro 21H2 Qt 6.7.3 Libtorrent 1.2.19.0 ### What is the problem? I've been downloading torrents to a temp drive, then moving to another drive when finished, to defragment them. This causes lots of downtime 'coz you can't download to a temp drive and copy from that drive to the destination drive at the same time. So I tried checking "Download parts in sequential order", unchecking "Use another path for incomplete torrent" so they'd download to the destination drive, and downloading just 1 file at a time, to see how much fragmentation I'd get. I did this en masse to dozens of queued downloads that hadn't been started. I found my destination drive was filling up twice as fast as it should, without downloading any more files than expected. What happened was that when I unchecked "Use another path for incomplete torrent" for a torrent that hadn't started downloading yet, qB "moved" it to the destination drive (no actual moving involved, cuz they hadn't started), then CHECKED THE BOX AGAIN and changed the path for incomplete torrent to be the same as the path for "Save at". I noticed this, and tried again to uncheck the "Use another path for incomplete torrent" for these torrents, since it now pointed to exactly the same directory as "Save at". But every time I unchecked it and then clicked "OK", and I immediately re-opened the torrent options window, I saw it had checked it and changed the incomplete directory again. I tried changing the incomplete path to a different directory, clicking "OK", opening the torrent options window again, seeing that it had done that correctly, then unchecking the box, clicking "OK", and opening the torrent options window again. The box had always been unchecked again and the incomplete torrent directory changed to match the final Save At directory. So I just let it run, figuring it would just leave the downloaded torrent files where they were when it was done. Yes it did, but... After downloading each complete .!qB file in the directory for incomplete torrents, it copied it to the "Save at" directory without the .!qB torrent, without noticing that the destination directory WAS THE SAME DIRECTORY, and without deleteing the .!qB file. So I ended up with two complete copies of each downloaded file in the destination directory, one ending in ".!qB" and one not. ### Steps to reproduce See above. ### Additional context _No response_ ### Log(s) & preferences file(s) I couldn't find which log file contains relevant information, because my log files filled up with 300,000 lines like this: "(I) 2025-04-14T03:04:16 - Performance alert: 1499000: performance warning: max outstanding piece requests reached. More info: https://libtorrent.org/reference-Alerts.html#enum-performance-warning-t"