Hi,

recently I encountered a possible bug when using ktorrent. Version was 2.2.2, but as I downloaded the torrent a while ago it's maybe a bug in 2.2.1 (which I used back then, nevertheless some seeding was done with 2.2.2).

Some details: The torrent contains 4 files, A to D.
A and C are small (approx. 1kB), B is huge (several GB), D is 100 MB, chunksize is 2 MB.
There are two chunks spanning several files.
One chunk spanning A and B, and one spanning B, C and D. I deselect D and downloaded only A, B and C. When the torrent finished according to ktorrent files A, B and C were completely downloaded.
Now I rechecked on a different PC using Azureus 2.5.4. Azureus claimed that the chunk spanning B, C, and D was missing, thus C wasn't downloaded at all and B was crippled, as a part in the end was missing. Unfortunately I didn't have a look if file C was present or not, but started the download again in Azureus and finished it.

Maybe someone could verify this (can't post the corresponding torrent file). It appears to me that the spanning chunk was wrongly associated only with the deselected file and therefore omitted.

Edit: It might be the case that Azureus accounts such chunks differently, i.e. the downloaded files were complete, but, as file D was deselected, the spanning chunk incomplete and Azureus just didn't show the pieces of the chunk in the downloaded files. Any thoughts on this?

Azureus doesn't know where KT stored the D part of that chunk. So the chunk is incomplete and AZ has no way to verify the hash.