mldonkey, a multi-networks file-sharing client - Bugs: bug #35509, wrong ed2k commit when downloading...
You are not allowed to post comments on this tracker with your current authentication level.
bug #35509: wrong ed2k commit when downloading file through both ed2k and BT
Submitter: | Hin-Tak Leung <htl10> | ||
Submitted: | Sat 11 Feb 2012 07:38:18 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | Program malfunction | Status: | None |
Assigned to: | None | Open/Closed: | Open |
Release: | 3.1.0 | Release: | 3.1.0 |
Operating System: | Linux | Binaries Origin: | CVS / Self compiled |
CPU type: | x86_64 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Downloading the same file through ed2k and BT. It wasn't obvious from the beginning, since the two protocols uses different hashes.
When download through BT finishes, the incomplete ed2k file also get committed but is wrong. This can be shown by actually running ed2k_hash on the BT-downloaded file (which shows that it has the correct ed2k hash), while ed2k_hash on the ed2k-downloaded file has a different and wrong hash. Also, the ed2k-downloaed file is still sparse, by running "du" on it, on linux.
It appears that the ed2k commit logic gets a bit confused when the BT-originned file turned up in incoming/files ?