recheck integrity doesn't work as it should

Bug #1709866 reported by Sopor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AirDC++
New
Undecided
Unassigned

Bug Description

After downloading 14 rar files i found out that two of them was broken (crc error). I then used the 'Recheck integrity' from the download queue and i could see in the system log there was two files broken:
[2017-08-10] [13:39:43] Integrity check for the bundle Xxxxxx.Xxx.X.S24E21.720p.HDTV.x264-XxXXX started (total bytes to check: 660,00 MiB)
[2017-08-10] [13:39:44] S:\tv-hd-x264\Xxxxxx.Xxx.X.S24E21.720p.HDTV.x264-XxXXX\xxxxxx.xxx.X.s24e21.720p.hdtv.x264-xxxxx.r12: calculated CRC32 does not match the one found in SFV file.
[2017-08-10] [13:39:45] S:\tv-hd-x264\Xxxxxx.Xxx.X.S24E21.720p.HDTV.x264-XxXXX\xxxxxx.xxx.X.s24e21.720p.hdtv.x264-xxxxx.r05: calculated CRC32 does not match the one found in SFV file.
[2017-08-10] [13:39:47] Integrity check finished for the bundle Xxxxxx.Xxx.X.S24E21.720p.HDTV.x264-XxXXX: 0 B of failed segments were found.

I could alse see in the download queue that one bundle was moved from Finished to Queued (i can see the number ( 1 )) but there is no bundle name. Nothing more seems to happen. The files is still broken.

It seems that file r05 is in use by 'NT Kernel & System'. I don't know why this file was in use by 'System' but i was forced to reboot the computer to remove the lock. If this wasn't AirDC fault there should at least be some kind of check if a file is in use to prevent this in the future.

AirDC 3.42a-19

Revision history for this message
Sopor (sopor) wrote :
Revision history for this message
Sopor (sopor) wrote :

After i restarted the computer and those two broken files was removed i did a new 'Recheck integrity' i can now see the bundle in Queued (1) and status Rechecking and when it was finished no files was downloaded (so it won't download missing files?).

I then re-added those broken files and did a new 'Recheck integrity' and the same thing happening again except it didn't lock the file but it didn't fixed those two broken files. The Queued (1) was empty but still it showed there was one bundle Queued.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.