Version 1.2 RC2
Im using KDE 3.5, partition downloaded to was of type FAT32.

Anyway, I started to download a torrent. Speed shows like 900KiB/s for 5-10Mins. I check the status and it says it has only downloaded 30MB.
So I check the folder, and its not true. Its 230MB.
Well impossible to download..
I closed ktorrent and wiped config files. ~/.kde/share/config/ktorrentrc and ~/.kde/share/apps/ktorrent folder.
Start ktorrent again, import & convert ip-filters.
And tried importing these 230MB of data. It imported and now status was that I had only downloaded 8MB.

The bug with importfileplugin is that it seems too make a duplicate of the data inside the folder in a new folder with the same name.

If you ask me, I wonder why you even have this as a form of "import plugin" For me it seems like very very unsafe not to be able to verify data contents. Like in other programs you can do a "check" whenever you want. And the whole data is checked. (This is what the import does I know, but whats the point of having it separated from the rest of the system? Just brings more bugs)
If it was like this you could throw away the import and just make a check before torrent is downloaded. More natural and more user-friendly if you ask me.

EDIT: Just so clarify some, I tested the importfile with a lot of torrents. ranging from 5GB to 100MB.
There are NO weird chars in the filenames.

Fuel wrote:Version 1.2 RC2
Im using KDE 3.5, partition downloaded to was of type FAT32.

Anyway, I started to download a torrent. Speed shows like 900KiB/s for 5-10Mins. I check the status and it says it has only downloaded 30MB.
So I check the folder, and its not true. Its 230MB.

The order of downloads is random, And when we download a chunk at the end of the file, we will immediatly put that chunk at it's right location. So this is very logical, we expand the file when we need to, and fill in the chunks when they are dowloaded. So filesize does not amount of bytes downloaded.

900 KB/s for 10 minutes that should get you 500+ MB, and you only get 30, if you had not deleted your log file, we could see if you got lots of poisoned chunks.

Well impossible to download..
I closed ktorrent and wiped config files. ~/.kde/share/config/ktorrentrc and ~/.kde/share/apps/ktorrent folder.
Start ktorrent again, import & convert ip-filters.
And tried importing these 230MB of data. It imported and now status was that I had only downloaded 8MB.

That is possible, if the torrent contains lots of files (lots of MP3's for example). Border chunks (i.e. chunks which lie in 2 or more files) will not get downloaded directly, but are stored in a file named current_chunks inside your temporary directory (which you deleted). Once they are complete, they get written to the final location.

Further we will also download the first chunk of media files (audio and video) first so that the preview feature can work as fast as possible. So you might be downloading lots of border chunks in the beginning.

The bug with importfileplugin is that it seems too make a duplicate of the data inside the folder in a new folder with the same name.

Learn the difference between symlinks and files.

If it was like this you could throw away the import and just make a check before torrent is downloaded. More natural and more user-friendly if you ask me.

You want KT to check you're entire disk for data which might potentially match with a torrent ?????

George wrote:

The bug with importfileplugin is that it seems too make a duplicate of the data inside the folder in a new folder with the same name.

Learn the difference between symlinks and files.

Code: Select all

ivan@ivan01 ~/win/down/Homevid2005 $ ls -lh
total 48K
drwxrwxrwx  5 root root 16K Jan 21 20:48 Homevid2005
drwxrwxrwx  2 root root 16K Jan 21 20:46 cd1
drwxrwxrwx  2 root root 16K Jan 21 20:47 cd2


I know you probably have a lot of people asking stupid questions and stating foolish things. But please don't underestimate me, I am a programmer just like you.
Edit: also one thing I noted when the 5GiB torrent did this, I ran out of space and ktorrent crashed and could not be started again before space was freed.

The order of downloads is random, And when we download a chunk at the end of the file, we will immediatly put that chunk at it's right location. So this is very logical, we expand the file when we need to, and fill in the chunks when they are dowloaded. So filesize does not amount of bytes downloaded.

This explains the filesize. Although im pretty sure that I downloaded a lot more then 30MB. Next time, Ill post log.

You want KT to check you're entire disk for data which might potentially match with a torrent ?????

No, only where you choose to save the data. Almost every torrent program works like this.

Seems to be another bug with downloading..

Started a download, downloads okay..
(100-200KiB/s speed)
after like 20mins it goes down to 5-6KiB/s even though there was ~30 leechers and ~250 seeders. (connected to 6 leechers and 30-40 seeders)
after 30 mins more it is still on 5-6KiB/s.
Just out of curiousity. I stopped the download, closed ktorrent. And resumed with azureus. after 1-2 min with azureus I had stable 100KiB/s and 5 mins after that around 400KiB/s.

Fuel wrote:

George wrote:

The bug with importfileplugin is that it seems too make a duplicate of the data inside the folder in a new folder with the same name.

Learn the difference between symlinks and files.

Code: Select all

ivan@ivan01 ~/win/down/Homevid2005 $ ls -lh
total 48K
drwxrwxrwx  5 root root 16K Jan 21 20:48 Homevid2005
drwxrwxrwx  2 root root 16K Jan 21 20:46 cd1
drwxrwxrwx  2 root root 16K Jan 21 20:47 cd2


I know you probably have a lot of people asking stupid questions and stating foolish things. But please don't underestimate me, I am a programmer just like you.

I though you were refering to the cache dir, my brains wasn't really turned on when I read your post. I appologize. The problem is that one variable in the stats file is wrong. The files created are just empty.
It's now fixed in the svn version.

Edit: also one thing I noted when the 5GiB torrent did this, I ran out of space and ktorrent crashed and could not be started again before space was freed.

Got a backtrace ?

This explains the filesize. Although im pretty sure that I downloaded a lot more then 30MB. Next time, Ill post log.

Speed calculation is pretty accurate, so I think lots of bad chunks. If you have peers sending you garbage data at high speed, you can see this in the log file, you should have lots of hash verification errors.

No, only where you choose to save the data. Almost every torrent program works like this.

Sort of like an auto import, when there is a matching file or directory structure. We could add that in the future.

Fuel wrote:Seems to be another bug with downloading..

Started a download, downloads okay..
(100-200KiB/s speed)
after like 20mins it goes down to 5-6KiB/s even though there was ~30 leechers and ~250 seeders. (connected to 6 leechers and 30-40 seeders)
after 30 mins more it is still on 5-6KiB/s.
Just out of curiousity. I stopped the download, closed ktorrent. And resumed with azureus. after 1-2 min with azureus I had stable 100KiB/s and 5 mins after that around 400KiB/s.

Could be a bug. Sometimes your download speed is dependant on one big seeder, and if that one decides to choke you, you have a problem.

However if you have a healthy download, you are downloading from several peers at a decent speed, if one chokes you, you still have the other. So in this case this would be a bug.

Got the new 1.2 release a few days ago.
Still seems to be problems with downloading.

There is that download problem wich seems to occur sometimes.
It occured last night, download speed was ~1MB/s up until 94% where it drop to 20-70kB/s (wich I thought was strange since this torrent had 90 seeders and 0 leechers), again I switch to azureus and download the last 6% with ~950kB/s.

No backtrace sorry, I'll get one next time (the full partition crash, wich seems to have been fixed now)

Fuel wrote:Got the new 1.2 release a few days ago.
Still seems to be problems with downloading.

There is that download problem wich seems to occur sometimes.
It occured last night, download speed was ~1MB/s up until 94% where it drop to 20-70kB/s (wich I thought was strange since this torrent had 90 seeders and 0 leechers), again I switch to azureus and download the last 6% with ~950kB/s.

No backtrace sorry, I'll get one next time (the full partition crash, wich seems to have been fixed now)

Sounds like the bug several other people have reported, where at the end of the download things stall out. I haven't been able to reproduce this problem, that is why it isn't fixed.

I noticed that bug this morning: seeing a torrent with several seeders that was 99.96% I just waited around, but after 10 min, it was still "paused", with no active chunk, and a lot of upload activity...

I simply quitted ktorrent and restarted it, and first thing it did was to load the ultimate missing chunk.

the next two torrents went to 100% without problem