hello every one…
i’ve just upgraded my bitcommet 1.20 to 1.22 and when i’m downloading a file ..in the “log” tab i this error:
"2010.09.03 13:04:09 Downloaded piece failed in hash check, 1231 KB dropped. "
"2010.09.03 13:08:19 Downloaded piece failed in hash check, 2048 KB dropped. "
and it’s happened a lot…so can anyone tell me why this happened…although this problem weren’t in bitcommet 1.20???
thanx anyway..
This is not a bug. This is an error that occurs quite commonly when for any reason the piece which was downloaded has some corrupted data in it and fails hash-check. This is the mechanism that BitTorrent protocol uses to make sure that the final file you get is exactly identical with the original one.
You can also see the amount of dropped (garbage) data downloaded, in the Summary tab by hovering the mouse in the Transfer area, over the Download Size value.
This issue is addressed in the Wiki FAQ: What is “rubbish data” and why am I downloading so much of it?
HI there!!
So is there any way to minimize the error ??
Cause in my case, it sometime continuously giving me this error for more thn 10-20times…
Please help!!
Thanks in advance.!!!
You can’t really minimize it, and transmission errors do tend to happen this way - none at all, or a whole bunch. Computers in general retry many times because most transmission errors are transient. (Disk read errors are handled this way too.)
It isn’t a particular bother most of the time though, since either an ungarbled message will get through, or the client will eventually decide to get the piece elsewhere. Being able to do that latter is one of the things that makes bittorrent so robust.
It’s only when you get the same error on the same packet over and over, and you’ve got all the others, and this has been going on for quite a while (subjective calls, all three of these) that suspicion arises of other factors that have to be dealt with. A few routers were making translation errors due to bad design, in the earlier days of bittorrent, and they would cause things like this.
Mostly though, you can just ignore them and let your client handle things.