Opened 11 years ago

Closed 11 years ago

#4010 closed Enhancement (worksforme)

RFE - request peer name/ip for failed checksums

Reported by: Astara Owned by:
Priority: Low Milestone: None Set
Component: Transmission Version: 2.20
Severity: Minor Keywords:


I was looking in my transmission log and found 11 of these in a row, within a span of 7 minutes:

[13:55:17.981] My-broken-tor Piece 3622, which was just downloaded, failed its checksum test (peer-mgr.c:1468)

It is interesting how I got several in a row all w/one torrent -- it would be more interesting if I new which peer it was that sent me the broken pieces. Would it be difficult to add the hostname or IP of the peer that sent these? Would be interesting to know if they were all from the same client or from several clients. Being able to look at message like that over time I might figure out that some clients were bad or that I was having some persistent problem, depending on how much the peer varies.

After that spurt, I had about 7 fails over the next 3 hours spread over 5 torrents -- probably not abnormal, but the earlier spike was a bit weird.

Change History (1)

comment:1 Changed 11 years ago by jordan

  • Resolution set to worksforme
  • Status changed from new to closed

Several peers typically participate in filling out a piece, so determining which of them is the "bad" one is problematic.

Transmission uses a "strikes" policy where a peer that participates in too many bad pieces is automatically banned. This can be seen in the debug messages:

"peer %s contributed to corrupt piece (%d); now has %d strikes"


"increasing peer %s strike count to %d"

and finally

"banning peer %s"

So I think this is a request for something that's already implemented -- at least within the uncertainty of knowing which peer fed the bad block into the piece -- and am closing this ticket as "worksforme" to indicate it's already implemented.

Note: See TracTickets for help on using tickets.