search

qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
28.66k stars 4.01k forks source link

Having to force recheck often #3533

Closed Shadowfied closed 9 years ago

Shadowfied commented 9 years ago

qBittorrent v.3.2.1 - Win 10 x64 (issue happened on 8.1 as well)

I recently switched over to qBittorrent and I've been loving it. Everything works perfect, except for one huge issue. After reboots or computer down time, all torrents are back to 0.0% with the status "Paused". The files are still there, if I navigate to the destination all files work perfectly, and therefore, it makes me so freaking mad cause resuming a torrent makes it download again, and being part of several private trackers, you really have to consider how much you download. How can it download again (it's not re-checking, it¨s actually downloading) when the files are already there and fully complete? Instead, I have to pause them again, then do a force recheck, which currently takes about 10-20 minutes because of all content I have seeding.

The execution log shows this for every single torrent when it happens (with their respective names of course, duh)

8/1/2015 11:31:35 AM - Reason: Family Guy S10 1080p WEB-DL DD5.1 H.264-CtrlHD fast resume rejected: expected value (list, dict, int or string) in bencoded string 8/1/2015 11:31:35 AM - Fast resume data was rejected for torrent Family Guy S10 1080p WEB-DL DD5.1 H.264-CtrlHD, checking again...

I have googled and seen others with the same issue, all these issues are marked as closed and fixed though, which isn't particularly helpful.

Any ideas?

Thanks

sledgehammer999 commented 9 years ago

That error indicates an error in libtorrent. Can you update to the just released v3.2.2 and tell me if it was solved?

f3mo commented 9 years ago

Not solved. In my case, when I try rechecking the torrent, it starts re-downloading. The files got deleted.

sledgehammer999 commented 9 years ago

@crazy-hunter do you get the same error in the log?

Shadowfied commented 9 years ago

Just updated. Will post here if it happens again, in the mean time, thank you!

WaterSibilantFalling commented 9 years ago

I have this problem, in v 3.2.3.

Repeatidly retorrenting the same sets of files because, at some time, they are re-determined to have not been downloaded. Unfortunately, though, checking - force recheck - does not find or seem to even be able to see these files.

Then, the downloading starts again. I am now torrenting a 407 MB audiobook for the third time.

But, if the checking worked - if the force rechecking could see that the files were there, complete, but still with th *.!qB suffix - then this could be easily fixed: when a user sees that a formely complete file is now starting to download again, then a force recheck.

* Ah, I just discovered something.* There are maybe six audiobooks that have this multiple download problem. Four of these audiobooks have, now, two copies of each: (1) one downloading for the second or more time, in the "Download Here" directory, and (2) one of each that has been copied on completion to the "Completed here" + "label" directory. The one in the "Completed here" + "label" directory still has its .!qB suffix and, while it can play as an mp3, is not actually complete, has four or five little glitches - probably individual transfer packets missing. Anyway, the hash check of these files could not possibly have been correct before each (set of) file(s) was moved to the "Completed here" + "label" directory. ... AND they all still have their .~qB suffix in the "now I am complete" directory, from which they would, normally, start seeding.

One other complete audiobook has just dissappeared, though qBittorrent gui was saying that it was 100%. I then tried to check it, and after doing so 4 or 5 times, it has gone back to 0% and started downloading again (but the seeders have gone, they'll come back)

I hope this helps.

StephaneTardif commented 9 years ago

v3.2.3 on Windows 8.1 on one tracker, I become un-connectable after 20 to 30 minutes according to the tracker. restarting qbit helps as well as force recheck. I think it started after I updated from v3.2.2 to v3.2.3. I customized the file location. I personally do no see duplication. I do not see errors in the execution log. Each torrent show as seeding.

sledgehammer999 commented 9 years ago

Closing because original problem has occurred again for 16 days. @RichardWilliamPearse your problem is unrelated and fixed by the upcoming v3.3.o. You can try the beta builds from the forum. @StephaneTardif you're problem is unrelated too. You might be experiencing #3473