Large file upload poorly handled

[Michael]

I was trying to upload a large (7.5gb) iso image. After some point the file size at the remote location was decreasing versus increasing. Resume does not understand how much of the file has been previously uploaded and eventually uploaded 11gb for a 7.5gb file. If the upload is made in a single continuous session the result is OK, but for example a local file of size 7,960,723,456 is reported as 692,211,136 at the remote site in FileZilla. Actual size at remote site is 7,960,723,456

[Jim Michaels]

I am having a somewhat different problem with a 4.01GB file @ 15-34KB/s over a period of 2-3 days with connection breakage and server resets.

I set the resume to 99 times so I could get the job done.

the file uploads to about 80% from the next-to-last time I checked, and then the next time I checked it was at 0% yet when I connected and got a file listing, filezilla said the resulting file was at 3,161,622,112 bytes. so I did something I usually do when something goes wrong, I turn off the queue, wait, and turn it back on again. now it shows as 80.0% again. the previous downloading was thrown away apparently. I hope my DVD ISO doesn't end up as swiss cheese. only a download and a comp command will tell.

the server is running pureftpd, so it makes temporary files, possibly in all cases, maybe not in all cases, I don't know for all resumes.
if I can, I will try to upload a debug ftp log.

[Jim Michaels]

snippet of Jim Michaels' ftp log, 4/25/2010

[Jim Michaels]

by the way, I downloaded the file from my web site and compared it to the original and all came out fine despite the oddities with the progress indicator.