Deluge 1.2.3 - completion, one step forward two steps back
Posted: Wed Apr 14, 2010 7:39 am
Hi All,
Deluge 1.2.3 on Ubuntu 9.10 Server.
I've been noticing it more and more commonly lately that a file will begin downloading normally, only to reach a certain point (it's different for each) where the percentage completion level jumps backwards.
This loop will continue until I delete the torrent and file from my disk and redownload it. Forcing a recheck will cause the completion percentage to revert to 0%. The file will then stickj again in a similar spot to before. Torrent files are coming from different sources so I do not believe they are the cause. All trackers are set to default to Openbittorrent (flexget strips out tpb, which I find to be patchy).
To illustrate - foo.bar will be at 33.24% complete, then go to 32.40%, back up to 33.74%, then back to 31.24%. (for illustration purposes only, not actual samples)
The numbers seem to change constantly, its not at any fixed point that the regression occurs. If I do not stop the file, it will continue to loop until I do. Last night a 175MB file stuck around 30% then used up 12GB of my download limit just looping as shown above.
I'm at a loss to explain it. Any hints?
E.E.
Deluge 1.2.3 on Ubuntu 9.10 Server.
I've been noticing it more and more commonly lately that a file will begin downloading normally, only to reach a certain point (it's different for each) where the percentage completion level jumps backwards.
This loop will continue until I delete the torrent and file from my disk and redownload it. Forcing a recheck will cause the completion percentage to revert to 0%. The file will then stickj again in a similar spot to before. Torrent files are coming from different sources so I do not believe they are the cause. All trackers are set to default to Openbittorrent (flexget strips out tpb, which I find to be patchy).
To illustrate - foo.bar will be at 33.24% complete, then go to 32.40%, back up to 33.74%, then back to 31.24%. (for illustration purposes only, not actual samples)
The numbers seem to change constantly, its not at any fixed point that the regression occurs. If I do not stop the file, it will continue to loop until I do. Last night a 175MB file stuck around 30% then used up 12GB of my download limit just looping as shown above.
I'm at a loss to explain it. Any hints?
E.E.