qBittorrent contributing to potential data loss when always resuming torrent after recheck when payload is not found #16118

New issue

Open

opened 2026-02-22 02:48:51 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-22 02:48:51 -05:00

Owner

Originally created by @slrslr on GitHub (Sep 30, 2024).

Suggestion

From time to time, You find some errored torrents because you have renamed or relocated files using your OS file manager and forgot that these files are part of some torrent.

So in qBtittorrent (I am using latest 5.0.0 AppImage Libtorrent 2) You go to the errored torrents section. Change location of the torrent payload, but you accidentally set incorrect path or the payload file is still named differently. Then you click to recheck. The file disappear from the errored section so you loose track of it and must be lucky to remember its correct name to filter it out of the long torrents list.

Second problem, for which I have created this issue is that in case the torrent payload is not found during recheck, user have to be quick enough to find the torrent and stop it before it start downloading (because qbt sets it to a downloading state), so it often (in my case IMO always) qbt starts writing the data you usually already have in a different location. Maybe qbt can set that torrent as stopped or back as errored so user have it handy for next attempt?

Instead user finds resumed or downloading torrent and makes a second attempt to set the correct path or tries to rename the payload file name/s. During this qbt relocates incomplete payload and overwrites complete files downloaded earlier! https://github.com/qbittorrent/qBittorrent/issues?q=is%3Aopen+is%3Aissue+label%3A%22Data+loss%22

Conclusion:
I see it as a smaller problem to set torrent as stopped (or back as errored) than 1) enabling data loss, 2) wasting data transfer by resuming download from zero and also 3) causing duplicity on disk.

Use case

No response

Extra info/examples/attachments

No response

Originally created by @slrslr on GitHub (Sep 30, 2024). ### Suggestion From time to time, You find some errored torrents because you have renamed or relocated files using your OS file manager and forgot that these files are part of some torrent. So in qBtittorrent (I am using latest 5.0.0 AppImage Libtorrent 2) You go to the errored torrents section. Change location of the torrent payload, but you accidentally set incorrect path or the payload file is still named differently. Then you click to recheck. **The file disappear from the errored section so you loose track of it and must be lucky to remember its correct name to filter it out of the long torrents list**. Second problem, for which I have created this issue is that in case the torrent payload is not found during recheck, user have to be quick enough to find the torrent and stop it before it start downloading (because qbt sets it to a downloading state), so it often (in my case IMO always) **qbt starts writing the data you usually already have in a different location**. Maybe qbt can set that torrent as stopped or back as errored so user have it handy for next attempt? Instead user finds resumed or downloading torrent and makes a second attempt to set the correct path or tries to rename the payload file name/s. During this **qbt relocates incomplete payload and overwrites complete** files downloaded earlier! https://github.com/qbittorrent/qBittorrent/issues?q=is%3Aopen+is%3Aissue+label%3A%22Data+loss%22 Conclusion: I see it as a smaller problem to set torrent as stopped (or back as errored) than 1) enabling data loss, 2) wasting data transfer by resuming download from zero and also 3) causing duplicity on disk. ### Use case _No response_ ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Data loss

labels

2026-02-22 02:48:51 -05:00

deekerman commented

2026-02-22 02:48:58 -05:00

Author

Owner

@HanabishiRecca commented on GitHub (Sep 30, 2024):

Set Settings > Downloads > Torrent stop condition to Files checked.

@HanabishiRecca commented on GitHub (Sep 30, 2024): Set `Settings` > `Downloads` > `Torrent stop condition` to `Files checked`.

deekerman commented

2026-02-22 02:48:58 -05:00

Author

Owner

@slrslr commented on GitHub (Sep 30, 2024):

I already have it set that way. For some reason, yours described option does not work for me for this particular case. I remember though that it worked for newly added torrents.

@slrslr commented on GitHub (Sep 30, 2024): I already have it set that way. For some reason, yours described option does not work for me for this particular case. I remember though that it worked for newly added torrents.

deekerman commented

2026-02-22 02:48:58 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 25, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**