Minor files size discrepancy = verification failure

[GoogleCodeExporter]

What steps will reproduce the problem?
This one is hard to reproduce as it is a very specific case. Essentially, if 
the disk-reported file size is different to the torrent-stored file size, 
verification fails (even though the file is complete and correct).

Might even be caused to to a couple of bytes difference after renaming the file 
causing the reported file size to be 1MB less.

Example:
* Torrent-stored file size = 431MB
* Disk-reported file size = 430MB
* Verify action will fail

What is the expected output? What do you see instead?
I would expect the file to verify correctly for a tolerable difference in file 
size. Not sure how this could be done, or what a 'tolerable' difference would 
be considered as being. If I load the same file into uTorrent it successfully 
verifies though, so it might be worth looking at how they handle it.

What version of the product are you using? On what operating system?
5.0.1 Win7

Please provide any additional information below.

Original issue reported on code.google.com by aerosa...@gmail.com on 25 Jun 2014 at 10:59

[GoogleCodeExporter]

Even more confusion now. This appears to only apply when the torrent is added 
as a seed for an already existing file (e.g. the file was downloaded but the 
torrent was previously removed / the file was downloaded using a different 
torrent client), or where the file is renamed after the download has completed.

If the torrent is downloaded in transmission and the file is renamed *as part 
of the download process*, it verifies correctly even with the disparity in file 
sizes.

Original comment by aerosa...@gmail.com on 25 Jun 2014 at 11:32

[GoogleCodeExporter]

I think you'll need to describe the issue with more detail. Same as with #801

"If you are describing a scenario where you are renaming files/directories 
through the transmission daemon then I might think that this is a bug in the 
daemon. I can't exactly tell from the description the exact procedures you are 
using but there are some reported bugs possibly related."
 i.e. https://trac.transmissionbt.com/ticket/5656#comment:3 

Original comment by s...@yourfreemail.info on 26 Jun 2014 at 3:39

[GoogleCodeExporter]

This issue can be closed. I am not sure what the problem was with the specific 
torrents I noticed the issue on, but everything seems to be working now and the 
files are verifying even with the minor difference (including the ones that 
were previously failing!). It is either an intermittent bug or something weird 
on the local setup that has somehow corrected itself.

Original comment by aerosa...@gmail.com on 26 Jun 2014 at 9:36