I have run into a problem and while I'm not sure that it's due to ktorrent, I figured I'd ask around and see if anyone has experienced it.

Recently when downloading large torrents (1gb+), they will show 100% completed but when the data check scans it will find missing chunks and always show 99.90% completed. It will then restart, download the missing chunks, show 100%, do a data check, show missing chunks and 99.90% again.

I first noticed it while downloading an Ubuntu .iso (I tried nearly a dozen) and finally had to download it on a different system. Recently it's also done it with a 7gb+ torrent of .rar files.

For the record, all my smaller torrents (single tv episodes, etc.) seem to be working fine.

I'm running 64-bit Ubuntu Intrpeid 8.10 and ktorrent 3.2beta1.
I've tried changing the download location to each of my 2 hard drives and both are formatted ext3.

now it seems to be getting stuck at 99.71% on even small torrents (175 mb)

anyone have any ideas?

update 2:
I just restarted the computer and those 2 at least finished to 100%.

update 3:
I lied. Only one of them completed, the other is now stuck at 98.17%

And for the record, I'm connecting to plenty of peers and nearly maxing out my downloads so that's not the issue here.

update 4:
I was watching the torrent with the "chunks" tab showing and it kept showing the same chunk and I'd download 2, 12, 23, 28, of 32 then it would restart back at 2. After about 5 times it finally completed the download.

Do you see any hash verification errors in the log ? (~/.kde4/share/apps/ktorrent/log)

Not that I can see, but I do have a lot of this:

Wed Dec 3 08:53:54 2008: Resetted chunk 1
Wed Dec 3 08:53:54 2008: Resetted chunk 2
Wed Dec 3 08:53:54 2008: Resetted chunk 3
Wed Dec 3 08:53:54 2008: Resetted chunk 4
Wed Dec 3 08:53:54 2008: Resetted chunk 5
Wed Dec 3 08:53:54 2008: Resetted chunk 6

I haven't duplicated the issue yet today and I don't know how to find my log from yesterday, sorry.

edit:
I'm seeing a lot of this too:

Wed Dec 3 12:30:23 2008: Connection closed
Wed Dec 3 12:30:24 2008: Unnecessary piece, total unnecessary data : 8.0 MB
Wed Dec 3 12:30:24 2008: Piece cache: memory in use 16.0 MB, memory freed 48.0 KB

Along with a lot of timeouts occuring and a lot of authentication failures.

ok, well it just did it again while downloading the newest episode of the Daily Show from EZTV.

Here is a cut of my log file showing what's going on. Hopefully it makes more sense to you guys (George).

Wed Dec 3 17:01:22 2008: Doing tracker request to url : http://denis.stalker.h3q.com:6969/annou ... 6d%b83%ac9
Wed Dec 3 17:01:22 2008: Checked 256 chunks
Wed Dec 3 17:01:23 2008: PEX: found 13 peers
Wed Dec 3 17:01:23 2008: PEX: found 50 peers
Wed Dec 3 17:01:23 2008: Previously OK chunk 29 is corrupt !!!!!
Wed Dec 3 17:01:23 2008: QM Starting: The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:23 2008: Starting download The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:23 2008: Loading list of peers from /home/nemo/.kde/share/apps/ktorrent/tor3/peer_list
Wed Dec 3 17:01:23 2008: Loading 0 active chunk downloads
Wed Dec 3 17:01:23 2008: DHT: Doing announce
Wed Dec 3 17:01:23 2008: Doing tracker request to url : http://denis.stalker.h3q.com:6969/annou ... 6d%b83%ac9
Wed Dec 3 17:01:23 2008: Initiating connection to 125.193.63.76
Wed Dec 3 17:01:23 2008: Initiating connection to 69.158.185.143
Wed Dec 3 17:01:23 2008: Initiating connection to 71.191.230.207
Wed Dec 3 17:01:23 2008: Initiating connection to 71.7.233.166
Wed Dec 3 17:01:23 2008: Initiating connection to 79.79.19.61
Wed Dec 3 17:01:23 2008: Initiating connection to 79.79.9.43
Wed Dec 3 17:01:23 2008: Initiating connection to 79.81.25.240
Wed Dec 3 17:01:23 2008: Initiating connection to 80.109.100.237
Wed Dec 3 17:01:23 2008: Announce ongoing, queueing announce
Wed Dec 3 17:01:23 2008: DHT: Got 16 potential peers for torrent The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:23 2008: DHT: Got 3 potential peers for torrent The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:23 2008: DHT: Got 8 potential peers for torrent The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:23 2008: DHT: Got 17 potential peers for torrent The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:24 2008: DHT: Got 10 potential peers for torrent The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:24 2008: DHT: Got 2 potential peers for torrent The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:24 2008: PEX: found 10 peers
Wed Dec 3 17:01:24 2008: Doing scrape request to url : http://denis.stalker.h3q.com:6969/scrap ... 6d%b83%ac9
Wed Dec 3 17:01:24 2008: Doing tracker request to url : http://denis.stalker.h3q.com:6969/annou ... 6d%b83%ac9
Wed Dec 3 17:01:24 2008: Not enough data received, encrypted authentication failed
Wed Dec 3 17:01:24 2008: Authentication to 79.79.19.61 : failure
Wed Dec 3 17:01:24 2008: Initiating connection to 79.79.19.61
Wed Dec 3 17:01:24 2008: Request timed out 18760 65536 16384 BitComet
Wed Dec 3 17:01:24 2008: Piece cache: memory in use 21.3 MB, memory freed 48.0 KB
Wed Dec 3 17:01:24 2008: DHT: Got 12 potential peers for torrent The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:24 2008: Request timed out 18706 1998848 16384 Azureus 4.0.0.4
Wed Dec 3 17:01:24 2008: Piece cache: memory in use 12.2 MB, memory freed 96.0 KB
Wed Dec 3 17:01:24 2008: Scrape : leechers = 724, seeders = 1786, downloaded = 297
Wed Dec 3 17:01:24 2008: Doing scrape request to url : http://denis.stalker.h3q.com:6969/scrap ... 6d%b83%ac9
Wed Dec 3 17:01:24 2008: DHT: Got 12 potential peers for torrent The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:25 2008: DHT: Got 8 potential peers for torrent The.Daily.Show.2008.12.02.DSR.XviD-YesTV.[VTV].avi
Wed Dec 3 17:01:25 2008: DHT: AnnounceTask done
Wed Dec 3 17:01:25 2008: Authentication to 79.81.25.240 : ok
Wed Dec 3 17:01:25 2008: Sending ping request to 79.81.25.240:26000
Wed Dec 3 17:01:25 2008: Not enough data received, encrypted authentication failed
Wed Dec 3 17:01:25 2008: Authentication to 98.235.34.191 : failure
Wed Dec 3 17:01:25 2008: Initiating connection to 98.235.34.191
Wed Dec 3 17:01:25 2008: Authentication to 79.79.19.61 : failure
Wed Dec 3 17:01:25 2008: Initiating connection to 118.213.10.57
Wed Dec 3 17:01:25 2008: Scrape : leechers = 704, seeders = 1725, downloaded = 291
Wed Dec 3 17:01:25 2008: Authentication to 71.191.230.207 : failure
Wed Dec 3 17:01:25 2008: Initiating connection to 71.191.230.207
Wed Dec 3 17:01:25 2008: Authentication to 80.109.100.237 : ok
Wed Dec 3 17:01:25 2008: Timeout occurred
Wed Dec 3 17:01:25 2008: Authentication to 71.237.196.251 : failure
Wed Dec 3 17:01:26 2008: Initiating connection to 189.61.118.224
Wed Dec 3 17:01:26 2008: PEX: found 2 peers
Wed Dec 3 17:01:27 2008: Authentication to 71.191.230.207 : failure
Wed Dec 3 17:01:27 2008: Initiating connection to 24.122.209.198
Wed Dec 3 17:01:27 2008: Request timed out 1886 2719744 16384 µTorrent 1.8.1.0

stopping and restarting ktorrent multiple times didn't seem to have an effect, but once I restarted the computer, the torrent completed the download.

Sorry to keep posting with the possibly useless updates but I'd like to figure this out and I'm still not even sure that it is ktorrent related although browsing through the forums reveals that this same problem happened somewhere around the 2.1 release I believe.

Anyhow, thanks.

I have seen this issue quite some times, mainly seen if KT has crashed or been terminated improperly (ie kill -9 <####>, then the current chuck fails and doe not get resumed properly

Try do this:

Well start KT (duh)
Stop the torrent if it isnt already
Check data, it will find and mark the chuck as bad, sometimes you need to delete the broken file before it fixes the corrupted chuck(s) but not always.
Start torrent

Thanks Jesper, I'm guessing that was the problem...

Of course I can't be sure because I have a habit of rash moments of overkill and...well...I reinstalled my OS.

Since all of my docs are on a separate hard drive it didn't matter too much.

I installed the kTorrent version in the Intrepid repos (3.1.2 I think) and when I tried to resume the downloads that were acting up, the problem persisted. But when I deleted it and started from scratch it seemed to work fine.

So that tells me at least that it was a problem with kTorrent probably not shutting down properly.

Oi. What a headache. But man I do love me some kTorrent.

Everything was working fine with 3.1.2 so I figured I'd play with 3.2beta1...
...same problem again with the first torrent I tried it on.

And the second.

Perhaps there's a bug somewhere in there between ktorrent, intrepid, or 64-bit, I dunno.

Oh well, back to 3.1.2 for now.

I just wanted to post my solution so nobody thinks it was kTorrent, it wasn't.

Turns out my network card was **** out and corrupting all traffic.
I've replaced the card and had 6 successful downloads with no issues and am successfully using 3.2beta1 again.