Jump to content

Hash checks - fails


Recommended Posts

Something strange related to the latest bug of B 426->7 of multiple hash errors:

this was related to the diskio.coalesce_write --> I've noticed that when running B 425 and B 427 - this setting is being reversed. How come ? does it reflect a problem ?

I also suggest to save for each torrent - the "wasted" data + "# of hash fails" that are currently shown only during DL. Those should be kept as we do keep a record of the data size and average speed.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...