Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force recheck not working : Linux (links to similar Windows and WebUI issues) #10668

Open
AbsurdMagpieScrutinies opened this issue May 19, 2019 · 12 comments

Comments

Projects
None yet
4 participants
@AbsurdMagpieScrutinies
Copy link

commented May 19, 2019

Please provide the following information

qBittorrent version and Operating System

Version 4.1.5 64 Bit
Linux 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linu
Reinstalled and re-tried before submitting this issue
Installed via aptitude, Debian's package manager

If on linux, libtorrent and Qt version

Qt 5.11.3
Libtorrent 1.1.11.0
Boost 1.67.0

What is the problem

with complete downloads

Force Recheck simply does not work. At all.
The files are there, complete (or mostly complete).
force recheck does nothing at all.

with complete downloads, listed as 0% in qbittorrent

The same.
The path to the content is the same, and correct.
The downloaded files are present and readable.
Force Recheck returns instantly, leaving the files as 0% in the qbittorrent display

What is the expected behavior

The downloaded files are rechecked.
Complete files become 100% checked and continue seeding
Incomplete files are checked and display their degree of completion.
Complete files do not incorrectly show 0% complete.

Steps to reproduce

Try "force recheck" on any downloaded files.

Extra info(if any)

The files are stored on removeable media (1TB drive accessed over usb, mounted by udev). I can't see any mounting, unmounting problems.

Similar bugs, via the WebUI and on Windows:

libtorrent discussion

@a-raccoon

This comment has been minimized.

Copy link

commented May 19, 2019

Force Recheck issues were fixed in 4.1.6. Try beta 4.1.6 r4 or above, or wait for 4.1.7.

@a-raccoon

This comment has been minimized.

Copy link

commented May 19, 2019

Separate issue. If qBittorrent is expecting part files (*.!qB files) from a torrent you added, you will have to rename the completed files that you import to the download directory to have the .!qB extension. Or disable part files in QBT settings before adding the torrent / magnet.

@AbsurdMagpieScrutinies

This comment has been minimized.

Copy link
Author

commented May 19, 2019

So, this ticket should be closed?

BTW, 4.1.6 is the version in buster (testing currently becoming stable) in Debian

Sorry: 4.1.5 is the version in buster (testing currently becoming stable) in Debian

@thalieht

This comment has been minimized.

Copy link
Contributor

commented May 19, 2019

In the recheck department, 4.1.6 just stopped rechecking torrents in parallel.
Of the top of my head, things that may affect rechecking is whether you

  • Do not create subfolder
  • Use temp folder
  • Use .!qB for incomplete files

Please share if you use any of these or a combination of them so i can try to reproduce and if successful, look around the code.

@a-raccoon

This comment has been minimized.

Copy link

commented May 19, 2019

I will agree that there are still bugs with recheck. As I stated above, and thalieht eluded to, QBT has difficulty discovering complete files depending on several different states of the client configuration and the torrent's completeness. QBT does not perform a very exhaustive search of complete files where one might expect to find completed files, so they end up not being recheck-able in the torrent's current [inaccurately incomplete] state.

QBT should do more to discover completed files in the myriad of plausible locations. Eg: Within the temp location, within the completed downloads location, within a folder, the category destination, .unwanted folders, with and without the .!qB part extension.

@lev777

This comment has been minimized.

Copy link

commented May 19, 2019

I can recreate the issue. I create sub-folder, do not keep incomplete in temp & do not use .!qb for incomplete files.

@AbsurdMagpieScrutinies

This comment has been minimized.

Copy link
Author

commented May 20, 2019

In my case:

  • I do use .!qB for incomplete files
  • incomplete files are kept in a temp directory
  • files create a sub-folder
  • it is the files that are not in the temp location that can't be 'force rechecked'
  • it the files in their final location, in the directory listed as their location in qBittorrent GUI, that can not be 'force recheck'ed
@thalieht

This comment has been minimized.

Copy link
Contributor

commented May 20, 2019

@AbsurdMagpieScrutinies i can't reproduce :(
Assuming you meant "torrents" instead of "files" because for me, all files in the torrent move to final destination from temp on completion.
@lev777 that's what i use all the time mostly without problems, well seldomly i get this problem but never something i couldn't fix. Unfortunately i can't remember what i did but i do know it was always something that i messed up.

I'm not saying there isn't a problem, maybe it's some other setting i can't think of...

@lev777

This comment has been minimized.

Copy link

commented May 20, 2019

Is there a way for me to debug log the force recheck process to shed some more light on exactly what might be going wrong. I would be very happy to find out it is an issue with a workaround as it is fairly regularly a thorn in my side.

@thalieht

This comment has been minimized.

Copy link
Contributor

commented May 20, 2019

Sorry i don't know.

@lev777

This comment has been minimized.

Copy link

commented May 20, 2019

Thanks, do you happen to know if there has recently been a debug build which had more logging enabled beyond what is enabled in a standard release?

@thalieht

This comment has been minimized.

Copy link
Contributor

commented May 20, 2019

No.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.