Pieces lying across file boundaries failing re-checks

[jgg5]

I'm running 1.8 under Windows XP, and I moved my torrent files and torrent content to directories on a different drive. The move basically worked correctly except for the following issue.

In some of my multifile torrents, a piece that spans the beginning of one file and the end of another file failed a forced re-check. Thus, I was left with two of the files in the torrent 99+% complete rather than the 100% that they were before being moved.

Is this a known issue, and is there a workaround?

[jewelisheaven]

... If it says not 100% complete it's not complete. Is it a a/v file? Those types of files have tags which more often than not are silently retagged by player/indexer/library software.

[Firon]

The file was either corrupted in the move, or was already altered by some application.

[jgg5]

Thanks for the replies.

I guess you must be right about something having corrupted the files, though all I did was use Windows to copy the files from one drive to another. Does Windows XP perform any kind of check (hash code or bit-wise file compare) after copying files? Or is that hoping for too much robustness from a Microsoft OS?

I had thought it was strange that this problem was arising specifically in pieces of the torrent content that span a file boundary. But now that I think about it, if I understand the issue correctly, it would take just a single error at the end of one file or at the beginning of the next to corrupt the entire piece that spans the file boundary, thereby causing both files to come up short during a re-check.

[jewelisheaven]

You can tell WHERE there's an error by using piecesize, finding the last full piece of your starter file... counting bytes til EOF and piecesize - bytes counted in new file. If you have a large piecesize it may be alot of data.

[Firon]

Nope, Windows doesn't verify anything after a copy/move.