waltherbans wrote:again there are some .fastresume-files but most torrents (~70%) don't have .fastresume-files
I just updated to 0.5.8.5 a few hours ago (rechecking every single file of course, on Ubuntu 7.10) and I also see very few .fastresume-files. In fact the only files that DO have fast resume are those that are not downloaded 100%. (5 or 38 torrents have fastresume, which exactly matches the ones not seeding).
I would try to restart Deluge again, to see if it the second time again will recheck every seeding file, but I'm afraid that it will again take 4-6hours to recheck everything (0.x TiB data...) and right now I'm seeding some things in high demand I just downloaded myself.
For the record, it also appears that last downloaded = last to be rechecked, which effectively would make me off-line on these newest most in demand files for the longest period of time. Irrespective of when this gets fixed, wouldnt it be a good idea to make (future valid) rechecks work in the order "latest downloaded first to be checked" sincefresh files are much more likely to be in high demand of sharing?
BTW, since I'm posting anyway, are you aware of that Deluge seems to report high upload speeds partially as DOWNLOAD to trackers?
As an example I have 1 file that has slowly crept up to +7% downloaded since I completed the download, presumably simply from counting the 0.1-2 kB/s transfer acks... (>40:1 ratio). Since many trackers are private and you need to keep your ratio high, Deluge haemorrhaging ratio like this is very bad.