Hello.
Mandriva 2006
rejserfs3
KDE 3.4.2
Ktorrent 2.03 rebuilded from cooker source rpm(ktorrent-2.0.3-1mdv2007.1.src.rpm)

I got this message after succsessful finished torrent and choosed "Check Data Integrity" .
About 12 percents of chuks are corrupted. Then this chunks were reloaded again, and I got this message for the same chunk numbers again. Corrupted chunks are at the beginning and at the end of the downloaded iso image. This is big torrent (4.33GB). I had tried 3 big torrents and got this messages for all of them. And md5 summs did not match. Is it tracker(torrent), or Ktorrent issue?
Regards.
Andrew

Better not true... can you point to or give me the torrent so i can verify and spare the devs some time?

stoeptegel wrote:Better not true... can you point to or give me the torrent so i can verify and spare the devs some time?

Please check e-mail
Regards
Andrew

Thank you kamand, i'll download it now. Will report somewhere this Saturday.

kamand wrote:I got this message after succsessful finished torrent and choosed "Check Data Integrity" .
About 12 percents of chuks are corrupted. Then this chunks were reloaded again, and I got this message for the same chunk numbers again. Corrupted chunks are at the beginning and at the end of the downloaded iso image. This is big torrent (4.33GB). I had tried 3 big torrents and got this messages for all of them. And md5 summs did not match. Is it tracker(torrent), or Ktorrent issue?

I experience this same problem with almost all of my downloads, although it's only 1 or 2 bad chunks, and usually just 1. It's always the same chunk for that particular download, (eg now chunk 150, for a different download it was chunk 632, for another 1476) There are lots of attempts to re-download that missing or corrupt chunk, but they almost always fail.
In addition, the downloads want to stop at 99.90%, due to that one bad chunk.

Rebooting seems to solve the problem, and eventually get the whole 100% that passes the data integrity check...but sometimes it requires multiple reboots (just restarting kde isn't sufficient). Obviously, this is a real pain.

The problem is not the particular downloads or it wouldn't happen with so many downloads from various trackers and even those with dozens of peers and seeds. It has to be ktorrent itself.

I'm on kubuntu 6.06 on an amd64 system. KTorrent version is 2.0.3, gotten as part of of the kubuntu desktop on top of ubuntu lamp server, from the synaptic package manager. KDE version is 3.5.2.

Hmm, to me this problem smells like either:

(1) Bad RAM -- use memtest86 to find out for sure
(2) Faulty routers -- try a direct internet connection. Some routers, especially the cheaper ones, will consistently corrupt a specific chunk.

Took somewhat longer than expected, but svn has no issues here. I would test the points jdong mentoined.

jdong wrote:Hmm, to me this problem smells like either:

(1) Bad RAM -- use memtest86 to find out for sure

memtest - OK. And memtest does not guarantee that memory is ok. But I dont see any indications about bad ram.

jdong wrote:(2) Faulty routers -- try a direct internet connection. Some routers, especially the cheaper ones, will consistently corrupt a specific chunk.

I dont understand this. I got message "Previously OK chunk XXXXX is corrupt !!!!!".
So received chunk was ok (I think received chunks already checked for correcteness), and was corrupted somehow later.
Regards
Andrew

I dont understand this. I got message "Previously OK chunk XXXXX is corrupt !!!!!".
So received chunk was ok (I think received chunks already checked for correcteness), and was corrupted somehow later.
Regards

Before saving a chunk we obviously check if it is correct. Before we start uploading a chunk we also do a hash check of said chunk, to ensure that nothing has happened with it. And to ensure that we are not uploading bogus data.

Maybe you should do a file system check ?

George wrote:Maybe you should do a file system check ?

Thanx. I already done this. I`l try finish this torrent later.
Regards
Andrew

Hi,

I'm experiencing the "Previously OK chunk XXXX is corrupt !!!!!" messages as well. I am using ktorrent 2.0.3 and tried the snapshot from 28th Oct as well. The messages appear for several torrents. Chunks that have been reported corrupt appear as corrupt after they've been downloaded again. A filesystem check reported no errors.
Is there any solution to this or a fix underway?

Best regards,

M.

AFAIK(i am just some weird supporter) there are no known corruption issues with 2.1dev currently, that is i haven' t read any on forum or bugs.kde.org. If you could share the torrent you're having these issues on it would be great. Then i can check them out and at least verify whether we have a problem or not.

Btw, you might not wanna use 28 Oct snapshot; it has a bug when stopping the torrent. (but of course that's why they're called snapshots)

The torrent for which the problem occurs is:

http://torrent.ubuntu.com/kubuntu/relea ... so.torrent

(with current ktorrent 2.0.3, although I really liked the snapshot ^^)
BTW: To rule out possible filesystem problems I've used a freshly generated filesystem.

I have downloaded more then 400 MB of this torrent, and so far no corruptions.

EDIT: More then 500 now, still no corruptions

+1
I download the full torrent and got no problems with data.
Are you sure you don't have parts of both versions on your system?