mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Recheck only the selected file(s) #17010
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#17010
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 @jbruchon on GitHub (Jul 8, 2025).
Suggestion
In a torrent's file/folder list, I want to be able to right-click a file/folder or set of files/folders and have qBT run a data check ONLY on those files, not the entire torrent.
Use case
I am attempting to download several mostly-identical archive "tera-torrents" (near or above 1TB in size) that have a lot of identical files. I'm also combining incomplete identical files with different names using zeromerge. Both of these cases ("archive update" torrent sets and "I copied a more complete file in manually") cause updated file data to be written to common files, but qBT doesn't know anything about the new data. The only way to tell qBT about the data is a "force recheck" for the whole torrent. It would be better to be able to selectively recheck only specific files instead. Without making qBT aware of this new data, there can be a ton of unnecessary duplicate data being downloaded and written over itself.
As a sort of semi-automated extension of this request, it would also be nice if a torrent like this could be set as a "duplicated" torrent and qBT cache the last modified time for each file write, then detect if the file time changes and automatically perform a recheck on that file to become aware of any new data.
In both cases, such a recheck ignoring the pieces that qBT knows were already completed would be helpful. Adding selective rechecking ability may also be helpful in implementing one of my requests from five years ago: #13556
Extra info/examples/attachments
No response