Deluge Forum

Now, just having Deluge have to recheck all/some of the torrents every so often isn't that killer (although if you fix fast resume, that would be nice), as I just run it in the background, but now, I normal exit (not crash) deluge, and then re-opened next day, and one of the files I was seeding (ratio was 0.89 something) had to be rechecked (stupid bug in fast resume), so okay, I wait for it to recheck, blah, blah, rechecks, but then, unlike other finished ones, after the recheck, the ratio doesn't jump from 0.000 back to what it was, it stayed at 0.000, basically forcing me to re-upload again 200 Mb....!!!!!

not bothering to update until 0.6 comes out (the 0.5.8.8 thing annoyed me, so I'll wait for 0.6)

Also, I noticed the ratios are broken. At 1.000 share ratio, when I looked, the number of total MB uploaded was 1 MB short of the amount the file size was...when the file was already completely downloaded and seeding so.....it was 1.002 when it equaled. Now 0.002 isn't that big of a difference, and I don't know anything about coding, but I can't help wonder why the simple math of uploaded:downloaded is wrong. I mean, when uploaded = downloaded, it should be 1.000, not 1.002 (or something else, depending on file size, may vary, I don't know)...I would think it has to do with the synchronizations of the various panels though (because I've noticed on the main area, the "speed" still shows something for a torrent while at the same time, the number of bytes uploaded/downloaded in the first tab isn't moving when a connection slowly comes to a end)

you should try 0.5.8.9, it has some changes to fast_resume.

as for the upload ratio,
it's more likely the file is taking up an exta MB on your HDD than the upload ratio being incorrect.

If its 1 MB more on the HDD than said on deluge, then its the downloaded number's error, either way, its some sort of error......(or the data could just not be refreshing as often as it should) also, had a fun CTD on launch-up today, and relaunched, all torrent fast resume data were lost ><
for some reason though, I've noticed, when the 'deluge has encountered a error' box pops up, if you ignore that box, deluge stays open and working, but everything done during that time is lost (ex I seeded like 200 Mb this way because I didn't feel like closing it, and then next start up, those 200 mb weren't counted anymore)

And 0.5.8.9 seems to have broken fast resume too according to the forums, so I'll wait until 0.6.0.0 (anyway, on wikipedia, it says 0.5.8.7 is still supported)