I've just been downloading a torrent from a reliable, private tracker using build 1.06+ (5179) on OS X 10.5.2 over a 1MBit connection, connected to between 190-200 peers of 200 discovered. This is my failed data:
180.5MB is with sample, which I de-selected to get the below number of 174.7MB.
Massive!
I'm just trying to download 174.7MB (selected). All but half-a-dozen of the people I'm connected to are seeders (the rest are around 96%+ done); the majority of peers are using uTorrent, the second largest pool being Azureus, and a sprinkle of other clients, including Transmission.
I usually notice quite a bit of failed data in Transmission, but this is a new high (or new low?).
Ever since this incident I've been keeping a closer eye on 'Failed DL', and it's a little disturbing. Right now, for instance, on just one torrent I 'Have' 568MB with a 'Failed DL' of 109.5MB. That's not far off 20%. On another torrent, of 188.0MB verified there's a 'Failed DL' of 77.2MB -- over 40%!
I've been finding that these aren't uncommon amounts (and percentages) to have in 'Failed DL', even on private trackers.
Does anyone else have this? Do you keep an eye on it?
I've got a test patch in r5241 to address one possible cause for this.
I'm not sure what the real cause is yet, since it's difficult to get it to happen reliably. At this stage I'm just inspecting the code and going after a piece that seems like a likely suspect..
2.7GB of downloaded data, plus 630MB of failed download. Piece size is 4MB, and the torrent is made up of two 1KB files, and a single 7GB file. It is the only torrent running.
Transmission seems to failing and discarding data at the hash check when the data should instead be passing.
The little status bar (underneath Transmission's toolbar) told me that I had downloaded 500KB. The inspector is showing 30MB less "Have" data, but 40MB greater verified data. 28MB of data has failed in this time.