Ktorrent 1.2 works fine for me (except some initial problems, see below), indeed it works so fine that my harddisk reached the limit of its capacity by now...

I downloaded some files from a multifile torrent according to my diskspace and burnt the iso-files onto CD-ROMs. Now I want to delete the files and download the rest.

Will I run into problems if I simply delete the downloaded files? (I guess that Ktorrent still tries to seed them, right?)

If I uncheck the files in ktorrent, the files vanish from the download directory.
However, they still occupy disk space as they are merely moved into the Ktorrent cache directory and simply replace the link that was previously there. I guess that deleting them manually from the cache is a bad idea either, right?

So what should I do to free disk space? Do I have to stop and remove the torrent and start over again (forefeiting partially downloaded files)?

Thanks for any adivce!
(And, no, I cannot add another harddisk since I am on a laptop...)

----------------------------
Some unrelated feedback:

* I also encountered the "stalled at 99%"-problem reported in other threads here, though restarting ktorrent once every day did always help for me.

* My connection has an upload of 32kb/s and download of 256kb/s; however ktorrent usually reports average upload speed of ~20kb/s and download of only ~10kb/s. Is it normal to already reach a ratio of 2 without any seeding? (encountered for various torrents)

* Ktorrent was incredibly slow in the beginning. I double-checked to open the ports in my router's firewall and diverting them to my laptop; however I forgot that my linux laptop has its own firewall by default. Maybe I am a single case, but maybe this is something for the FAQ to say (ie. Firewall on router and machine), since Ktorrent did work without, albeit slowly.

* I checked the posts and links here about "choked" and "snubbed", but I still do not get it, since the info widget shows arbitray combinations (like uploading to clients marked as choked and receiving from clients marked as snubbed). I thought "snubbed = yes" means that I did not receive something from that client; while "choked = yes" means that I do not want to send something to that client? Even the other way around makes no sense either if compared to actual up/download-rates...

At the moment we still allocate all diskspace, even for not downloaded files. Manually deleting the files can result to problems when border chunks (chunks which lie in 2 files) get downloaded.

I still need to deal with this in a better manner, but I have so many other things to do, so I don't know when I will get to that.

* I checked the posts and links here about "choked" and "snubbed", but I still do not get it, since the info widget shows arbitray combinations (like uploading to clients marked as choked and receiving from clients marked as snubbed). I thought "snubbed = yes" means that I did not receive something from that client; while "choked = yes" means that I do not want to send something to that client? Even the other way around makes no sense either if compared to actual up/download-rates...

Choked means that the peer has choked you, it is still possible that you upload to that peer. And snubbed only gets updated when a piece has arrived.

I'm hoping the new niceness system will improve speeds. I'm gonna start on this after encryption is finished.

What is it with this forum that makes spammers so attracted to it... i can't get it, this forum isn't that crowded and we aren't even the kind of people who will click on these links.

Am i missing something?

George wrote:At the moment we still allocate all diskspace, even for not downloaded files. Manually deleting the files can result to problems when border chunks (chunks which lie in 2 files) get downloaded.

Err, no, at least not in Ktorrent 1.2: The diskspace seems to be preallocated for each whole file only when the first chunk of that particular file arrives - or so...

At least, I could repeatedly watch my remaining disk space (using "df -h") shrink by the size of a newly enabled file of a multifiletorrent after a couple minutes has gone past. (With nothing else running that might consume that much disk space in that short amount of time.)

So my question still remains: Will deleting a downloaded file of a multifile torrent crash Ktorrent, even when it is not adjacent to a file which currently being downloaded?

Turtoise72 wrote:

George wrote:At the moment we still allocate all diskspace, even for not downloaded files. Manually deleting the files can result to problems when border chunks (chunks which lie in 2 files) get downloaded.

Err, no, at least not in Ktorrent 1.2: The diskspace seems to be preallocated for each whole file only when the first chunk of that particular file arrives - or so...

1.2 has no diskspace preallocation. It just grows the files as necessary.

So my question still remains: Will deleting a downloaded file of a multifile torrent crash Ktorrent, even when it is not adjacent to a file which currently being downloaded?

No but when a chunk needs to be written to a deleted files it will be recreated (and if it is the last the whole file will be allocated).