Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filesize of transfer incorrect, resulting in incomplete files #3804

Closed
cyberduck opened this issue Oct 12, 2009 · 2 comments
Closed

Filesize of transfer incorrect, resulting in incomplete files #3804

cyberduck opened this issue Oct 12, 2009 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Oct 12, 2009

605155f created the issue

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

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 12, 2009

605155f commented

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.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 16, 2010

@dkocher commented

Duplicate for #3771.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants