Page 1 of 1

How to fix rechecking of all torrents after rebooting?

Posted: Sun Feb 25, 2018 9:52 am
by minchia
I've recently started using qtorrent as an open source alternative to utorrent, but I'm stuck with this annoying problem:
I've got about 50 torrents. Every day after I start my PC (with Windows 10), qtorrent proceeds to recheck all my torrents.

Before I shut down my PC, I close qtorrent and wait for it to disappear from the process list (b.t.w. a visible "Please wait while shutting down..." window would be a useful feature here) to be sure all files are closed gracefully.
Then the next evening I start my PC, qtorrent proceeds to check all torrents. This takes so long, that there's not enough time to check them all before the evening has passed. This effectively makes qtorrent quite useless in my situation where the PC isn't left on permanently.
Is there a setting or something that can be done to prevent this unnecessary rechecking every time?

Re: How to fix rechecking of all torrents after rebooting?

Posted: Sun Feb 25, 2018 11:38 am
by kutalok
Maybe you have problem with .fastresume files, other program change its timestamps or delete its. Enable logging View -> Log -> Show all, and Options -> Behavior -> Log file and see messages.
Probably answer https://github.com/qbittorrent/qBittorr ... -365029955
Same problems:
https://github.com/qbittorrent/qBittorr ... -367260063
https://github.com/qbittorrent/qBittorr ... -364669593

Re: How to fix rechecking of all torrents after rebooting?

Posted: Sun Feb 25, 2018 2:17 pm
by minchia
Thanks for the links. In the log, I can see that about half the messages are about missing or invalid file sizes, and about half are about invalid timestamps. Both seem odd reasons. Unfortunately the log messages don't display the expected and actual timestamps and file sizes which would make recognizing a pattern or problem a lot easier.

I've had a similar problem in the past using rsync on NTFS where I had to adjust the timestamp window to make it work properly (as rsync uses a finer time resolution than NTFS or vice versa). The problem could be related to something like that but without the timestamp details in the log, it's hard to tell.