Ultima Posted April 25, 2007 Report Share Posted April 25, 2007 µTorrent can't tell when partial pieces are partial pieces, and when they are corrupt pieces -- it can only tell that the hash is different from the hash specified in the .torrent file. Link to comment Share on other sites More sharing options...
Guest Posted April 26, 2007 Report Share Posted April 26, 2007 It's a partial piece if it's not complete yet. Isn't that the purpose of resume.dat: to keep track of download progress? What does corrupt pieces have to do with anything? Corrupt pieces aren't an issue until the file is finished, when you hash it to make sure that it's okay. That's how most other P2P apps work.I think the confusion is in the purpose of checking. Your thinking seems to be that the only reason that a file would be checked is if there's corruption. Honestly I don't think that I've ever seen a check after a crash report that there was any corruption, they (µTorrent, eMule, etc.) have always done their little check and continued on as before the crash. Losing all unfinished pieces is not really worth a one-in-a-billion chance of actually getting any corruption. Even if there were a bit of corruption, then the post-download hash would detect it and download that one piece instead of having to download a couple dozen.Another reason for rechecks is when a file is coming in from somewhere else in tandem. For example, you may be downloading a file from a torrent, but also downloading the same file with another program, or perhaps even another torrent. All you have to do is to occasionally stop the torrent, do a recheck to detect any pieces that were downloaded from the other place, then continue on. That way the torrent(s) finishes faster and can begin seeding both sooner.Surely there must be a way to avoid losing partial pieces. Link to comment Share on other sites More sharing options...
Ultima Posted April 26, 2007 Report Share Posted April 26, 2007 AFAIK, incomplete pieces are never written to disk. Accordingly, resume.dat wouldn't keep track of incomplete pieces, but only which pieces are complete, and which pieces aren't. Link to comment Share on other sites More sharing options...
Smoovious Posted April 26, 2007 Report Share Posted April 26, 2007 incompletes are written to disk... between runs of the client, or reboots of the computer, so long as they didn't recheck due to a crash, the incompletes remain.-- Smoovious Link to comment Share on other sites More sharing options...
Ultima Posted April 26, 2007 Report Share Posted April 26, 2007 Apparently, that's not what I was told when I was writing the manual.Green means the data is still unwritten to disk. Incomplete pieces are never written to disk.This definitely isn't something I would've pulled out of thin air and put into the manual without first consulting someone... :|Edit: I am beginning to believe otherwise, though... I still see incomplete pieces in my Pieces tab after having restarted µTorrent. In that case, I'm leaning toward Synetech's side on the matter... Link to comment Share on other sites More sharing options...
Smoovious Posted April 26, 2007 Report Share Posted April 26, 2007 Might as well hang onto the partials... after all, soon as they complete, they'll get hashed anyways before being added to the rest, so they're safe.Plus, with all of the torrents made with 4Mb pieces?! >shudders<-- Smoovious Link to comment Share on other sites More sharing options...
Guest Posted April 26, 2007 Report Share Posted April 26, 2007 Exactly; piece sizes are growing and when you've got 50 4MB pieces half done… Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.