Filesize of transfer incorrect, resulting in incomplete files #3804
Comments
Additional info: The file actualy is 1.4GB, but I discovered the new Snow Leopard finder uses 1000 instead of 1024 as a basis (very annoying), which is why finder lists it as 1.57Gb. So the display in cyberduck's transferwindow is correct; still it is strange that the file even though transfered completely, misses the end at the destination. Might cyberduck internally have an incompatibility with snow leopard's way of calculating filesizes? As an experiment, I tried to drag the file over the already existing upload in cyberduck. It then offered me to resume (even though it uploaded it as complete earlier), and when I confirmed the resume, it transfered a few bytes and then gave an error about a filesize mismatch. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using cyberduck to upload content to a popcornhour box over FTP. I had a problem where episodes of a tv show would stop a minute before the end. After investigation, it appeared the file was incomplete.
In the screenshot you can see how I'm uploading a 1.57Gb file, which is listed as a 1.4Gb file in Cyberduck. It will only upload the first 1.4Gb and will then say 'transfer succesful'. No matter how often I try to upload this file, it will always show up as 1.4 in the cyberduck window. I've had several files with this problem. Several others didn't have the problem.
Attachments
Screen shot 2009-10-12 at 8.10.11 AM.png(64.9 KiB)The text was updated successfully, but these errors were encountered: