file data not being written to disk?

[fxyefx]

I've noticed a very strange problem I've been having with deluge, and I was wondering if anyone else has noticed a similar problem.
I'm running 0.5.8.7 on Ubuntu Hardy beta 64-bit.
As my torrents are downloading, the main progress bar updates normally; however, the progress bars for the individual files keep showing up as 0%, even after the torrent has completed downloading 50%+. Once the torrent is just about to complete, suddenly all the progress bars for the files update really quickly and go toward 100%. (and I can hear by hdd working a lot)
The real problem though is that if I pause a torrent that's, say, 50% complete, close and restart Deluge then do a force re-check, the torrent does not seem to know that it has downloaded any of the files and starts at 0% again!
My knowledge about this stuff isn't very advanced, but I suspect that Deluge isn't writing the data to the hdd until the very end of the torrent, and loses whatever data is in memory when closed (even if I pause the torrent first and give it time to do a write). Is there a way I can force deluge to write the data to the hdd as it goes along downloading?
I don't have this problem with Transmission, but I also never had this problem on ubuntu 7.10 - so perhaps it's a filesystem bug in the Ubuntu Hardy beta that's somehow specific to Deluge.

Thanks!

[siu4coders]

The same here, Ubuntu 8.04 Hardy Beta 64 bits with deluge 0.5.8.7 package from the main web.

Thanks!

[locketine]

Are you using an external hard drive by any chance or possibly a drive with spaces in its name?

if yes then change its name to a single word and it should start working fine for you. Folders can be named whatever you want to name them but the actual device as it appears in Places->Computer must be one word. I figured this out when my external would download but not save files but my local disk was.

Also, make sure to use the version of deluge on this website rather than the one in the package manager because it is missing many bug fixes and features that are in the current version.

[fxyefx]

Thanks for the input;
Unfortunately those things shouldn't be what's causing the problems I'm having - I'm using the latest package from this site, and the drive the files should be written to is a partition on one of my internal (SATA) drives. It's called "Stuff", so I'm pretty sure the naming scheme thing wouldn't be the issue. Hopefully some gvfs update will fix this (it seems like there's a new update of it each time I boot linux!)

[vinicius.vbf]

Exactly the same here. Ubuntu Hardy i386 (x32). Transmission working OK, I think it is a Deluge-exclusive problem. Any news on this?

[klaount]

I just discovered that i have the same problem here
I thought it was because of an external hdd I was using but no, same thing happens on my normal disks and it's not an issue of the diskname. This is a serious flaw :/

[benjaminzsj]

Same here , but this doesn't happen to every torrent, those small ones seem working fine.

[boteeka]

Same problem here. Runing Hardy, and latest deb (0.5.8.9) from Deluge site. I first found out that the file I was waiting for an hour to complete and finally I closed Deluge because it wouldn't finish, the nezt time I started Deluge it magicaly showed that it is finished indeed (and another two files after it too). But I only found out this when I restared Deluge. Before the restart it showd about 60%, and after the restart it jumped to 100% at once. And the file was downloaded correctly.

[benjaminzsj]

Hi all, I found that one simple solution is not to check the data before finish, but if the check is forced I really don't know what to do then.

[Snarkyone]

Holy Crap!!! This is not a good thing at all! I am not running a Linux OS but I am seriously worried that this is also going to occur on a Windows based system has there been any feedback on this happening on Windows systems, I use private trackers exclusively so this could be a very serious issue to me.