Opened 15 years ago

Closed 13 years ago

Last modified 9 years ago

#604 closed bug (WontFix)

Option to recheck downloads once complete

Reported by: anonymous Owned by: andar
Priority: minor Milestone:
Component: Core Version: 1.3.0
Keywords: Cc: johanvdb@…


I quite often have issues with completed torrents containing some corrupt files (usually larger torrents, say >1Gb).

This can currently be fixed by manually forcing a recheck from the right click menu and then downloading the corrupt pieces again (usually only 1-2%).

It would be useful to have an option to automatically recheck downloads when they complete and if errors are found add them back into the queue until the torrent completes without error.


Change History (4)

comment:1 Changed 14 years ago by Cas

  • Resolution set to wontfix
  • Status changed from new to closed

I do not see a reason for needing this.

comment:2 Changed 13 years ago by johanvdb

  • Cc johanvdb@… added
  • Resolution wontfix deleted
  • Status changed from closed to reopened
  • Type changed from feature-request to bug
  • Version changed from 1.0.4 to 1.3.0

Apologies for resurrecting an old thread, but I was hoping to find some feedback on my strange issue.

For some reason, about 10% of my torrents always end up corrupted. A re-check shows that some parts needed to be downloaded still, and then starts downloading again. Some times the process needs to be repeated 2 or 3 times before the file is fully complete and working. In all cases, when Deluge *thinks the file is finished, it moves it to the complete folder, sends a mail, and marks it as 100% + seeding, but running an md5 on the file clearly shows it is not binary complete.

So while I agree that the above sounds like a hack, I am unable to figure out another solution, and thus also vote for a recheck of downloaded files.

I have bumped the version to 1.3.0 as this is the default released with FC14. I have also changed this from feature request to bug as this is not really a new feature. If the bug didn't happen the "feature" would not be required.

Kind regards Johan

comment:3 Changed 13 years ago by Cas

  • Resolution set to wontfix
  • Status changed from reopened to closed

You should never reopen tickets that are this old.

This would be a libtorrent issue, if not something else with your OS, so you need to make sure you are using the latest version of 0.15.x and if it is still occurs open a ticket here

Also the latest version of Deluge is now 1.3.2

comment:4 Changed 9 years ago by mozreactor

This ancient bug still occurring in Deluge 1.3.10 (win xp x64)

I've opened a ticket with libtorrent as suggested

Note: See TracTickets for help on using tickets.