-
-
Notifications
You must be signed in to change notification settings - Fork 299
Transfers larger than 2**31 (2147483648) bytes fail #1235
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
Comments
Can you see the same issue with 2.8b1? The SSH library used is different in this version. |
Issue occurs with both 2.7.3 and 2.8b1. |
This looks like a server issue. The error message is given by the server. |
Oddly enough the upload worked with CrossFTP, another Java FTP client, as well as sftp. For this reason, I don't think it was the server. |
Can confirm this behavior with 2.8 (3256). As a workaround, I have resumed the transfer using 'rsync --partial --progress'. I doubt that this is because of the server: the file has been uploaded there from another Mac, by SFTP, using Transmit. Anyhow, for your information, the server's version string is 'OpenSSH_4.6p1 Debian-5build1, OpenSSL 0.9.8e 23 Feb 2007'. |
This is definitely a client bug. I was able to upload via the command line sftp client with no problem. |
As a workaround you might want to try SCP. Change the setting Cyberduck > Preferences > SFTP > File Transfers to SCP (SSH Secure File Transfer). |
Looking at the descriptions, it seems likely that these two tickets describe the same bug:
If the bug still existed in August 2007, why was the first ticket closed in May 2007 with "works for me"? |
When attempting to download more than 2147483648 bytes (Around 2 GB) Cyberduck gives the following error:
I believe that using an integer type that has a significantly larger capacity (such as a long) for the counter would solve this problem.
The text was updated successfully, but these errors were encountered: