qBittorrent
qBittorrent copied to clipboard
qbittorrent
Force Recheck hangs
qBittorrent & operating system versions
qBittorrent: 4.4.5 x64 Operating system: Windows 10 Home 21H1 x64 10.0.19043
What is the problem?
Force Recheck Hangs
When I tried 'Force Recheck' on all my torrents at once qBittorrent freezes. I did a restart, all torrents were checked as usual, but after that all torrents become green and go to 0%. Then nothing happens anymore. Restarted my PC several times, but nothing changes anymoer
Steps to reproduce
No response
Additional context
Status stays on "checking" and nothing happens
Log(s) & preferences file(s)
The logfiles says, for instance:
"(N) 2022-10-31T11:01:11 - 'Faure - Requiem; Bach - Partita, Chorales & Ciaconna (LSO - Tenebrae & Nigel Short, 2012)(LSO Live, 2012)(HD 24-96)' restored."
But apparently it is not restored....
Hi Priit,
It is version 4.4.5 I use a separate drive for my torrents and there are 2638 seedings. I do not use beta versions......
Kind regards,,
Henri
Van: Priit Uring @.> Verzonden: zaterdag 5 november 2022 09:51 Aan: qbittorrent/qBittorrent @.> CC: Apegapen @.>; Author @.> Onderwerp: Re: [qbittorrent/qBittorrent] Force Recheck hangs (Issue #17962)
When I tried 'Force Recheck' on all my torrents at once qBittorrent freezes.
This happens with libtorrent v1.2 or v2.0?
Are torrents to be checked on same drive as your OS?
How many torrents did you enable in settings to be checked at the same time?
Can you reproduce with qBittorrent v4.5.0beta1?
— Reply to this email directly, view it on GitHubhttps://github.com/qbittorrent/qBittorrent/issues/17962#issuecomment-1304445701, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARNYCJ4ZTLBKV23SKTIWDTLWGYNYTANCNFSM6AAAAAARS6P4VE. You are receiving this because you authored the thread.Message ID: @.***>
Hi Pritt,
All 2638 seeds were 'rechecked' After leaving the power on for 4 days seems to be 'normal' again. It appears that the rechecking was very, very slow: I could not see the progress, hence I thought everything was frozen...
I am afraid of beta versions as I am afraid to lose all my downloads/seeds, as this happened once, some time ago.
qBittorrent -> Help -> About -> Software Used:
Qt: 5.15.5 Libtorrent: 1.2.17.0 Boost: 1.80.0 OpenSSL: 1.1.1q zlib: 1.2.12
All the mentioned torrents were 100%
Next time I will follow your instruction: I am not so acquainted with this. all, sorry...
Hope I informed you well.
Kind regards, Henri
That's confusing, because you wrote in the beginning as if something became 0%, then maybe download was fast and didn't leave enough time to have them written to drive, which is odd.
qBittorrent said it was 0%, however, the torrents were in fact 100%
If qBittorrent or some other software is seeding, downloading and rechecking from slow HDD drive that's not an SSD or CPU is old or slow or low RAM, then that would make sense to be a reason rechecking takes long time. You can try running Windows Defragmenter, can help with reading and writing files in future if run it manually or atleast to recheck if it's disabled or not, good to check especially if you haven't enabled "Preallocate files" in qBittorrent settings.
I have a PC with AMD Ryzen 9 and 64GB RAM and Samsung SSD's ....... I indeed have enabled "Preallocate files" in qBittorrent settings
@Apegapen, @PriitUring Sorry, I can't comment on all this in detail (it's exhausting for me). Just one question. Don't you forget (or maybe you just don't know) what a "recheck" is? It simply tells torrent to reset all current progress and start from scratch, i.e. from the phase of checking (possible) existing files (i.e. the same as if you added a new torrent and pointed it to existing files). Therefore, it is not surprising that you see 0 progress. Since torrents are not checked all at once, you will see 0 progress for all of them, except for those that are being checked at the moment (their progress should increase from 0 to 100 percent as they are checked, since all files are on disk).
Therefore, it is not surprising that you see 0 progress. Since torrents are not checked all at once, you will see 0 progress for all of them, except for those that are being checked at the moment (their progress should increase from 0 to 100 percent as they are checked, since all files are on disk).
Oké, but with a fast PC with a Ryzen 9 processor with 12 Cores and fast SSD's one would expect to see some progress. But everything is clear by now: all those expensive fast processors with many cores are more marketing talk than fast action...
Oké, but with a fast PC with a Ryzen 9 processor with 12 Cores and fast SSD's one would expect to see some progress.
You don't see any progress at all? I.e. no one torrent is being checked? Then it may be some kind of problem related to the inconsistent state of the "resume data".
When I tried 'Force Recheck' on all my torrents at once qBittorrent freezes. I did a restart
What "restart" exactly do you mean?
If you still haven't fixed this situation in any way, could you provide a screenshot of what it looks like (the entire qBittorrent window)?
As I said earlier on: after 4 days under power, so 96 hours later, all worked again as expected...... So first I tried to restart qBittorrent and later on I restarted the PC. That did not help, but leaving the PC on for 96 hours was the solution.
Weird issue here starting with 4.5.0. Clicking re-check did nothing, issued a resume and the recheck started. Not certain if this is desired behavior in 4.5.0 because it's unexpected if you simply want to recheck the files without resuming.
@misantroop The problem you described clearly has nothing to do with this Issue. Nevertheless, this regression needs to be fixed ASAP. Could you create a separate Issue for it so that we can track it appropriately?
Hi Vladimir,
I think this is not actual anymore as I upgraded to version 4.5.0
Kind regards,
Henri
Van: Vladimir Golovnev @.> Verzonden: donderdag 8 december 2022 19:16 Aan: qbittorrent/qBittorrent @.> CC: Apegapen @.>; Mention @.> Onderwerp: Re: [qbittorrent/qBittorrent] Force Recheck hangs (Issue #17962)
@misantroophttps://github.com/misantroop The problem you described clearly has nothing to do with this Issue. Nevertheless, this regression needs to be fixed ASAP. Could you create a separate Issue for it so that we can track it appropriately?
— Reply to this email directly, view it on GitHubhttps://github.com/qbittorrent/qBittorrent/issues/17962#issuecomment-1343125411, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARNYCJ4TP5UWF7ZDLVBSK6TWMIQXBANCNFSM6AAAAAARS6P4VE. You are receiving this because you were mentioned.Message ID: @.***>
@misantroop The problem you described clearly has nothing to do with this Issue. Nevertheless, this regression needs to be fixed ASAP. Could you create a separate Issue for it so that we can track it appropriately?
I done it myself in #18187.
OK, thanks!
Kind regards,
Henri
Van: Vladimir Golovnev @.> Verzonden: vrijdag 9 december 2022 11:13 Aan: qbittorrent/qBittorrent @.> CC: Apegapen @.>; Mention @.> Onderwerp: Re: [qbittorrent/qBittorrent] Force Recheck hangs (Issue #17962)
@misantroophttps://github.com/misantroop The problem you described clearly has nothing to do with this Issue. Nevertheless, this regression needs to be fixed ASAP. Could you create a separate Issue for it so that we can track it appropriately?
I done it myself in #18187https://github.com/qbittorrent/qBittorrent/issues/18187.
— Reply to this email directly, view it on GitHubhttps://github.com/qbittorrent/qBittorrent/issues/17962#issuecomment-1344112343, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARNYCJ6NMTFK5UORK6RH4NDWMMA3TANCNFSM6AAAAAARS6P4VE. You are receiving this because you were mentioned.Message ID: @.***>
I started having have this issue in v4.5.0 QT5 (and some other issues).
Clicking "Force recheck" switches the torrent to "Checking" status and nothing happens. The HDD does not start to thrash. Clicking "Resume' sometimes helps.
My qbit also freezes when rechecking even a single torrent But I realized if I give it 20GBs of memory in settings -> Advanced -> Physical memory (RAM) usage limit then it works fine, but with my usual setting of 2GB it freezes. Outstanding memory when checking torrents is set to 1GB v4.5.1 Qt: 6.4.2 LibTorrent: 2.0.8.0
I've been having slowness (and freezes) during recheck (forced or after download is completed) for a very long time now, I think from earlier than 4.4 builds even. Right now I am using 4.5.2 with Qt 6.4.2 and LibTorrent 2.0.8.0, and I still have them. What I've noticed is that the issue occurs only with torrents that have video files in them. Often if the files are x265, but sometimes if they are x264. When the issue occurs the check is running extremely slow (for example 3-4GB file will be checked in roughly 5 minutes instead of maybe like 10 seconds), CPU usage sometimes goes up in spikes up to 80%, and UI freezes constantly. I think this may be somehow related to feature that allows us to stream media files, but this is just a hunch.
For reference, here's the media info for the latest file that caused (if required, I can share magnet link, but I'll be honest, this is a pirated content, so not sure if it will be ok to share it):
Format : Matroska
Format version : Version 4 / Version 2
File size : 4.25 GiB
Duration : 55 min 22 s
Overall bit rate : 11.0 Mb/s
Writing application : mkvmerge v49.0.0 ('Sick Of Losing Soulmates') 64-bit
Writing library : libebml v1.4.0 + libmatroska v1.6.1
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference fra : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 55 min 22 s
Bit rate : 9 991 kb/s
Width : 1 920 pixels
Height : 960 pixels
Display aspect ratio : 2.000
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.226
Stream size : 3.86 GiB (91%)
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Audio
ID : 2
Format : E-AC-3 JOC
Format/Info : Enhanced AC-3 with Joint Object Coding
Commercial name : Dolby Digital Plus with Dolby Atmos
Codec ID : A_EAC3
Duration : 55 min 22 s
Bit rate mode : Constant
Bit rate : 768 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 304 MiB (7%)
Language : English
Service kind : Complete Main
Default : Yes
Forced : No
Complexity index : 16
Number of dynamic objects : 15
Bed channel count : 1 channel
Bed channel configuration : LFE
Yep, increasing the RAM usage limit (from 512MB to 8192MB) fixed the problem for me too.
It seems there is some sort of state bug in here --
Selecting "Resume" makes the check happen, and everything goes on as normal. Selecting "Force Recheck" causes the file to sit in the Checking 0.0% queue forever.
Situation: I'm using USB disks. I got a NAS that I just moved all the USB disks to. Briefly, the disks were not available, as I had to reconfigure my docker volumes to work with the new locations of everything. This caused nearly everything in Q to show as "Missing Files", which I would normally run a "Force Re-Check" and it would spend a few minutes (to a few hours for large files) chugging along checking them, and then everything would be fine.
In this case, pressing Resume gets the Check going, and then it goes back to seeding once it's found.
qbittorrent v4.6.1 from the linuxserver/qbittorrent docker
update: this works, but it's also ignoring the "Max checks" setting in qbittorrent options, which is causing absolutely massive disk thrashing, and causing the NAS to start dropping things due to maxed out CPU and RAM. So I might need to run it on only 1 at a time, which means it will take forever to get my files back :D
and... one further update. almost definitely a confusion between paused torrent and active torrent, versus checking.
If I pause a torrent that is in the Missing Files state, then hit Force Re-Check, then it re-checks successfully, and it limits it to the number of max re-checks in settings. Otherwise, if I just resume, then it goes to the Checking state, and ignores the max re-checks setting.
If I just hit Force Re-Check on a Missing Files state, then it hangs at Checking 0.0, but Resume kicks it into working.
hopefully last update: with most of the torrents i've got showing "Missing Files", to get them to successfully re-check, I needed to:
1: Go to Errored tab 2: Select All 3: Force Re-Check 4: Once they all move to the Checking tab, shut down the docker, and restart it. This moves them from the "Missing Files" state, to the "Error" state 5: Select All 6: Force Re-Check
now they are running, and respecting the check limits
If I just hit Force Re-Check on a Missing Files state, then it hangs at Checking 0.0
Should be fixed by #20747.
Otherwise, if I just resume, then it goes to the Checking state, and ignores the max re-checks setting.
Are you sure it checks the hashes in this case? It is supposed to simply check for files without checking hashes.
Are you sure it checks the hashes in this case? It is supposed to simply check for files without checking hashes.
Couldn't tell you, I don't see a difference between Checking state either when attempting to resume a Missing Files, or doing a Force Check. Takes a long time, and thrashes the disks terribly if I get more than a couple going at once.
Only difference I can tell is that doing Force Re-check on missing files, results in 0.0 hang. Which is what this topic was about :) So, glad it's fixed. :)