Torrent download >100% complete about aria2

[tatsuhiro-t]

I think that indicator may go beyond 100% if piece containing the beginning of the or end of the file is shared by another file. But piece size is relatively small, aria2 will go into seeding mode in short time.

All I can reproduce is:
[#1 SIZE:49.5MiB/49.0MiB(101%) CN:1 SEED:1 SPD:767.6KiBs]
and in no time:
[#1 SEEDING(ratio:0.0) CN:0 SEED:0]

Download at one point reaches 100%, but then goes beyond 100% and is not complete: Neither is the download stopped
(or put into seeding mode) nor is it actually complete; there are still pieces missing.

Could you give me some more info:

• file size
• piece size
• actual indicator output
• possibly, torrent URI

[nmaier]

I think that indicator may go beyond 100% if piece containing the beginning of the or end of the file is shared by another file.

That's what I thought as first, too, but the file was only ca. 85% complete after manually checking the hashes.

But piece size is relatively small, aria2 will go into seeding mode in short time.

That didn't happen. In the end I waited for it to go to 112%.
(This one was select-file=39-41, followed by select-file=39)

Info Hash: b238cc6188ef249472ebda2c749a7b0807a58347
Piece Length: 4.0MiB
The Number of Pieces: 14387
Total Length: 57,547.8MiB (60,343,264,566)

[#1 SIZE:399.0MiB/356.0MiB(112%) CN:280 SEED:36 SPD:665.4KiBs UP:153.7KiBs(10,411.6MiB)]

aria2 version 1.15.1
** Configuration **
Enabled Features: Async DNS, BitTorrent, Firefox3 Cookie, GZip, HTTPS, Message Digest, Metalink, XML-RPC
Hash Algorithms: sha-1, sha-224, sha-256, sha-384, sha-512, md5

I did a similar thing with another torrent, where I

• started to download files 3,11,17
• then CTRL-C
• then resumed only 3 and waited for it to hit ca. 200%
• CTRL-C
• restarted with 3,11,17.

Using the original selection 3,11,17 again made the torrent finish successfully.

[tatsuhiro-t]

Thank you for the additional info.

I found the bug that aria2 wrongly adds up the completed length of incomplete pieces which is not in the current selection, but is in the previous selection. I think this explains the >>100% issue.

The bug fix is pushed in master branch.

[tatsuhiro-t]

I think 1.15.2 fixes this problem. If you still experience this issue, please re-open.