I'm trying to download one of the opensuse dvd images.
ktorrent says it's 100% done. The torrent isn't using any downlaod bandwidth, but is busy uploading it to somewhere else.
When I run the integrity check, it says that 330 chunks have failed/not downloaded.

1. How do I get *all* the chunks to download reliably?

2. Why doesn't ktorrent download/retry automatically?

I'm running KTorrent 2.1.4, using K Desktop Environment Release 3.4.2 level "b".

Can you send/link to the torrent?

I think you want: http://download.opensuse.org/distributi ... 86.torrent

>> say = "I love KTorrent"
Given that
1. it's taking 6 days to download a file that takes 12 with wget, and still doesn't missing 330 chunks and thinks it's done,
2. I've tried compiling the latest ktorrent, but get an error about some field not being a member of some structure. (Posted separately.)
3. Yast2 thinks that 2.1.4-1 is the latest version.
no, I don't love KTorrent. My feelings will probably change once I can get it to work.

Here you can get a 2.2.2 package for openSUSE 10.2. Unless you're using some other version.

KTorrent discards and redownloads all bad chunks it gets. However, your data might get corrupted when it is written (or not) to the disk, e.g. when you do a reboot without a clean unmount or your disk is failing. There is no after-completion automatic check in 2.2.2, but I think it is/will be implemented in the KDE4 port.

In your case, after running integrity check you should start the torrent again - KTorrent should redownload all missing data. Unless there are some other things (e.g. bugs) at play. That's why updating to the latest version is a good idea.

-edit-

Hey, stoeptegel. I had always found your signature a bit imprecise. It'd output "I *LOVE* KTORRENT", all uppercase.

Do you have an rpm for suse 10.0?

I have tried downloading the torrent in KTorrent, and it seems to re-hash to 100% in KTorrent, Deluge and azureus. So it is the expectation the failure is local.

stoeptegel wrote:So it is the expectation the failure is local.

Not quite so. I am seeing exactly the same problem here. After the download of the Opensuse DVD is finished and I do an integrity check, ktorrent detects between 300 and 700 broken blocks. I have reproduced this behavior 4 times already and I'm getting impatient. I have no IO errors on disk, not have I ever had any data corruptions on this system before. This is ktorrent 2.0.3 (Debian etch).

To be more precise: The failed blocks are always at the beginning and the end of the torrent. I have little knowledge of the torrent protocol - is it possible that some "bad guys" are trying to corrupt data (after all, this is a bootable DVD)?

Hmm. The OpenSUSE DVD is 4405843968 bytes long. That's 0x1069bd800, or 422 256k-blocks more than 0x100000000. Would it be possible that there is some sort of 32bit integer overflow?

I just downloaded the file again, and right after the "download finished" popup had appeared, I checked the integrty. Same result as before: ~170 of the first 400 blocks were corrupted. After that all is fine until about the last 400 blocks.

I bet there is an u32 overflow somewhere.

I haven't heard of this before, but you are using a really old version. I would suggest updating to the latest 2.2.2 version to see if the problem is resolved. There have been a lot of bug fixes and feature enhancements since 2.0.3.

Good Luck
Jeremy

Yeah, 2.0.3 is really old, and there were some problems with > 4 GB torrents. But those have been fixed.

As I said on 10/9:

2. I've tried compiling the latest ktorrent, but get an error about some field not being a member of some structure. (Posted separately.)
3. "smart" thinks that 2.1.4-1 is the latest version.

George wrote:Yeah, 2.0.3 is really old, and there were some problems with > 4 GB torrents. But those have been fixed.

Do you have a reference for the 4GB problems (bugzilla or similar, patch to fix?)

I'd like to post a bug report for the Debian 4.0 ktorrent package.

Here is the KDE bug report: https://bugs.kde.org/show_bug.cgi?id=132443

uncleremus wrote:

George wrote:Yeah, 2.0.3 is really old, and there were some problems with > 4 GB torrents. But those have been fixed.

Do you have a reference for the 4GB problems (bugzilla or similar, patch to fix?)

I'd like to post a bug report for the Debian 4.0 ktorrent package.

There were multiple fixes over time, and I'm not sure if you can just backport them to the 2.0 series.