starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

HD Killer: After "Relocating Files" Qbittorrent RE-checks terabytes worth of DATA on every program launch #9561

New issue

Closed

opened 2026-02-21 20:15:11 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-21 20:15:11 -05:00

Owner

Originally created by @rugabunda on GitHub (Dec 27, 2019).

Win 10 x64 1909; has been an issue for years now. For example:

After moving torrents to another drive from within QBitTorrent,
Closing QBitTorrent in the middle of and or moving them manually after & rechecking
Moving them manually then pointing qbit to the new folder

Even after checks are complete it ratardedly does it over, and over, and over, on every program launch, significantly wasting the life of the drive and slowing the drive down to a fraction of its original speed. This time it was 220 gb of files, however had I moved 14tb of files it would do the same thing... that is 2.333% of the life of a 600 TBW m.2 ssd upon each program load, or in my case nearly 7% of the drives lifespan/warranty; Its happened 3 times in a row and will continue if I don't pause them upon EVERY program load; previously it happened a dozen or more times before finally remembering/saving the checks. Until this is fixed I am forced to stop seeding, or better yet, use another app.

Originally created by @rugabunda on GitHub (Dec 27, 2019). Win 10 x64 1909; has been an issue for years now. For example: 1. After moving torrents to another drive from within QBitTorrent, 2. Closing QBitTorrent in the middle of and or moving them manually after & rechecking 3. Moving them manually then pointing qbit to the new folder Even after checks are complete it ratardedly does it over, and over, and over, on every program launch, significantly wasting the life of the drive and slowing the drive down to a fraction of its original speed. This time it was 220 gb of files, however had I moved 14tb of files it would do the same thing... that is 2.333% of the life of a 600 TBW m.2 ssd upon each program load, or in my case nearly 7% of the drives lifespan/warranty; Its happened 3 times in a row and will continue if I don't pause them upon EVERY program load; previously it happened a dozen or more times before finally remembering/saving the checks. Until this is fixed I am forced to stop seeding, or better yet, use another app.

deekerman

2026-02-21 20:15:11 -05:00

closed this issue
added the
OS: Windows
label

deekerman commented

2026-02-21 20:15:16 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Dec 27, 2019):

@rugabunda what version of qbittorrent?
Also looks like you did a force recheck??? yes?!

@xavier2k6 commented on GitHub (Dec 27, 2019): @rugabunda what version of qbittorrent? Also looks like you did a force recheck??? yes?!

deekerman commented

2026-02-21 20:15:16 -05:00

Author

Owner

@Mike-EE commented on GitHub (Dec 27, 2019):

@rugabunda

You cite 3 use-cases:
1 - Using qBt to move the torrents: I've never had a re-check problem with that, period. This shouldn't be an issue as long as your fast-resume and PART files are intact.
2 - Closing qBt "in the middle" of some unknown act - can you be more specific? Are you performing forced terminations of qBt? Fast-restore files that don't match disk files are going to, unsurprisingly, force qBt to perform a recheck.
3 - Manual moving then "pointing" them to a new folder. Again, can be more specific? Also note that rechecking after a manual move is design behavior - how else is qBt supposed to know which torrent pieces are available and which aren't?

It doesn't help anyone reading your post to understand what's happening when you don't cite the qBt version number you're using and you're not more descriptive of precisely how you're handling files when problems occur.

I think this falls under the "I want to do anything with files that comes into my head and I want qBt to figure out what I did by magic" category of complaints, which I think are exceeded in number only by "why can't qBt handle PART files like uTorrent" complaints.

@Mike-EE commented on GitHub (Dec 27, 2019): @rugabunda You cite 3 use-cases: 1 - Using qBt to move the torrents: I've never had a re-check problem with that, period. This shouldn't be an issue as long as your fast-resume and PART files are intact. 2 - Closing qBt "in the middle" of some unknown act - can you be more specific? Are you performing forced terminations of qBt? Fast-restore files that don't match disk files are going to, unsurprisingly, force qBt to perform a recheck. 3 - Manual moving then "pointing" them to a new folder. Again, can be more specific? Also note that rechecking after a manual move is design behavior - how else is qBt supposed to know which torrent pieces are available and which aren't? It doesn't help anyone reading your post to understand what's happening when you don't cite the qBt version number you're using and you're not more descriptive of precisely how you're handling files when problems occur. I think this falls under the "I want to do anything with files that comes into my head and I want qBt to figure out what I did by magic" category of complaints, which I think are exceeded in number only by "why can't qBt handle PART files like uTorrent" complaints.

deekerman commented

2026-02-21 20:15:16 -05:00

Author

Owner

@rugabunda commented on GitHub (Dec 31, 2019):

@rugabunda

2 - Closing qBt "in the middle" of some unknown act - can you be more specific? Are you performing forced terminations of qBt? Fast-restore files that don't match disk files are going to, unsurprisingly, force qBt to perform a recheck.

#1. I had closed QBitTorrent in the middle of using qBittorrent to move torrents from one drive to another drive; This may not be the exclusive cause, however it is the step I had followed to produce this issue.

#2. When I had closed qbit I then manually moved the files via windows explorer to finish what I had started inside Qbittorent. [I may or may not have manually run force re-check at this point, I don't remember, I blv files were highlighted in the red, so I may have; either way the problem happens]

#3. Listen carefully: Now the next subsequent recheck completed 35 minutes after loading qbittorent. However, upon closing and re-loading qbittorent, it still rechecks [only] the newly moved torrents every time I close and re-open qbittorrent, over and over again... the cycle continues

Listen carefully: Each time checking reaches 100% complete, if I close and open qbitorrent again it rechecks all over again.

3 - Manual moving then "pointing" them to a new folder. Again, can be more specific? Also note that rechecking after a manual move is design behavior - how else is qBt supposed to know which torrent pieces are available and which aren't?

It doesn't help anyone reading your post to understand what's happening when you don't cite the qBt version number you're using and you're not more descriptive of precisely how you're handling files when problems occur.

I am using the latest release, 4.2.1, this problem has been ongoing for the last year or more for myself, I always keep my apps up to date.

Sorry, it was a little confusing.

@rugabunda commented on GitHub (Dec 31, 2019): > > > @rugabunda > > 2 - Closing qBt "in the middle" of some unknown act - can you be more specific? Are you performing forced terminations of qBt? Fast-restore files that don't match disk files are going to, unsurprisingly, force qBt to perform a recheck. #1. I had closed QBitTorrent in the middle of using qBittorrent to move torrents from one drive to another drive; This may not be the exclusive cause, however it is the step I had followed to produce this issue. #2. When I had closed qbit I then manually moved the files via windows explorer to finish what I had started inside Qbittorent. [I may or may not have manually run force re-check at this point, I don't remember, I blv files were highlighted in the red, so I may have; either way the problem happens] #3. **Listen carefully:** Now the next subsequent recheck completed 35 minutes after loading qbittorent. However, upon closing and re-loading qbittorent, it still rechecks [only] the newly moved torrents every time I close and re-open qbittorrent, over and over again... the cycle continues **Listen carefully:** Each time checking reaches 100% complete, if I close and open qbitorrent again it rechecks all over again. > 3 - Manual moving then "pointing" them to a new folder. Again, can be more specific? Also note that rechecking after a manual move is design behavior - how else is qBt supposed to know which torrent pieces are available and which aren't? > > It doesn't help anyone reading your post to understand what's happening when you don't cite the qBt version number you're using and you're not more descriptive of precisely how you're handling files when problems occur. > I am using the latest release, 4.2.1, this problem has been ongoing for the last year or more for myself, I always keep my apps up to date. Sorry, it was a little confusing.

deekerman commented

2026-02-21 20:15:16 -05:00

Author

Owner

@rugabunda commented on GitHub (Dec 31, 2019):

I did a test moving a movie in qbit, letting it complete moving in qbit, then reloading qbit, it does not loop re-check. PASS!.
I moved the files manually outside of qbit, then opened qbit, then pointed qbit to the new folder... it said missing files, so I restarted qbittorrent. Qbit then began rechecking files without my forcing a recheck. Checking then completed.
upon re-loading qbittorrent, recheck loop occurs over and over.

At no time did i force a recheck, i merely moved the files.

@rugabunda commented on GitHub (Dec 31, 2019): 1. I did a test moving a movie in qbit, letting it complete moving in qbit, then reloading qbit, it does not loop re-check. PASS!. 2. I moved the files manually outside of qbit, then opened qbit, then pointed qbit to the new folder... it said missing files, so I restarted qbittorrent. Qbit then began rechecking files without my forcing a recheck. Checking then completed. 3. upon re-loading qbittorrent, recheck loop occurs over and over. At no time did i force a recheck, i merely moved the files.

deekerman commented

2026-02-21 20:15:16 -05:00

Author

Owner

@rugabunda commented on GitHub (Dec 31, 2019):

I think this falls under the "I want to do anything with files that comes into my head and I want qBt to figure out what I did by magic" category of complaints, which I think are exceeded in number only by "why can't qBt handle PART files like uTorrent" complaints.

If I made my bug report more like this here would it help?

@rugabunda commented on GitHub (Dec 31, 2019): > I think this falls under the "I want to do anything with files that comes into my head and I want qBt to figure out what I did by magic" category of complaints, which I think are exceeded in number only by "why can't qBt handle PART files like uTorrent" complaints. If I made [my bug report more like this here](https://vimeo.com/263461722) would it help?

deekerman commented

2026-02-21 20:15:16 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Feb 8, 2021):

@rugabunda This should be fixed in 4.3.3

Can you confirm?!

@xavier2k6 commented on GitHub (Feb 8, 2021): @rugabunda This should be fixed in **4.3.3** Can you confirm?!

deekerman commented

2026-02-21 20:15:16 -05:00

Author

Owner

@ghost commented on GitHub (Jul 17, 2022):

Issue was reported on a very old version. If anyone still experiencing this please comment to reopen or create a new ticket.

@ghost commented on GitHub (Jul 17, 2022): Issue was reported on a very old version. If anyone still experiencing this please comment to reopen or create a new ticket.