Holy failed data, Batman! 1.06+ (5179); OSX 10.5.2.
-
- Posts: 221
- Joined: Mon Oct 08, 2007 9:14 pm
Holy failed data, Batman! 1.06+ (5179); OSX 10.5.2.
Hey,
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?).
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?).
-
- Posts: 221
- Joined: Mon Oct 08, 2007 9:14 pm
I'm now using 1.06+ 5209.
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?
Thanks.
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?
Thanks.
-
- Posts: 221
- Joined: Mon Oct 08, 2007 9:14 pm
-
- Posts: 221
- Joined: Mon Oct 08, 2007 9:14 pm
I've just got r5244, so I'll test it out -- thanks for getting on this issue.
If you need me to run anything, or do anything, to give you a better picture of what's going on then I'll be more than happy to.
Thanks again.
Update: Okay, having just 'Downloaded' approx. 190MB, my 'Failed DL' increased by 148.9MB with build r5244. :/
If you need me to run anything, or do anything, to give you a better picture of what's going on then I'll be more than happy to.
Thanks again.
Update: Okay, having just 'Downloaded' approx. 190MB, my 'Failed DL' increased by 148.9MB with build r5244. :/
-
- Posts: 17
- Joined: Fri Feb 08, 2008 11:45 am
Dunno whether this is relevant or not, however today I had one torrent downloading by itself it finished with
which doesn't seem too bad.
I then started two more torrents which when finished had the following:
Is it possible that when Transmission is more active, more data fails the checks?
running build 5266
which doesn't seem too bad.
I then started two more torrents which when finished had the following:
Is it possible that when Transmission is more active, more data fails the checks?
running build 5266
-
- Posts: 695
- Joined: Wed Oct 31, 2007 6:11 am
- Location: Australia
Using Transmission r5314/5315.
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.
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.
-
- Posts: 221
- Joined: Mon Oct 08, 2007 9:14 pm
Using 1.06+ (5294) I just did this: 'Have' 350.6MB, 'Downloaded' 352.4MB ... with a 'Failed DL' of ... 0 bytes.
Update: later downloaded around 1GB of data, with a 'Failed DL' of 0 bytes.
Good going!
Update: later downloaded around 1GB of data, with a 'Failed DL' of 0 bytes.
Good going!
Last edited by publicfacing on Sat Mar 22, 2008 2:08 am, edited 1 time in total.
-
- Posts: 695
- Joined: Wed Oct 31, 2007 6:11 am
- Location: Australia