mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Do not move existing files to the incomplete downloads folder #17443
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#17443
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gallyamb on GitHub (Jan 11, 2026).
Suggestion
AFAIU, there is no any reason to move files from "completed" downloads folder back to the "incomplete" downloads folder when torrent is updated and re-added to the qbittorrent. We can just download files that are not equal to the files in a new torrent and then replace after successful downloading
Use case
When a tv show seeding organized via torrent file updating (and not via one torrent for each episode), downloading each new iteration of the torrent adds unnecessary pressure to the HDD, if qbittorrent is configured like this:
For now in the each iteration of torrent downloading the following happens:
If the feature request will be implemented, then only one full read will take place with no full write, only the updated files are written to the HDD
Extra info/examples/attachments
No response