Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Bug in re-check command
So I had a hard-drive filesystem issue and a file within a torrent got corrupted.  I tried re-check in Vuze and found the file that was corrupted.  I restored the file from backup and replaced the corrupted file, but Vuze won't detect that the file is replaced.  I tried re-check, clear allocation state, and clear resume data, and the file in the File Details view of the torrent still says it's only partially downloaded.

It almost seems like it's caching the file hash once, and then never updating the file hash again, even if the underlying file changes.
Is it possible that the file shares some edge state with another file that has been corrupted?

Possibly Related Threads...
Thread Author Replies Views Last Post
  failed hash check - Out of memory Largo 6 433 01-10-2017, 11:40 AM
Last Post: Largo
  Bug: total uptime counter wraps Spacey 0 270 12-03-2016, 11:49 AM
Last Post: Spacey

Users browsing this thread: 1 Guest(s)