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

Transfers larger than 2**31 (2147483648) bytes fail #1235

Closed
cyberduck opened this issue Aug 30, 2007 · 11 comments
Closed

Transfers larger than 2**31 (2147483648) bytes fail #1235

cyberduck opened this issue Aug 30, 2007 · 11 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Aug 30, 2007

2565d84 created the issue

When attempting to download more than 2147483648 bytes (Around 2 GB) Cyberduck gives the following error:

SSH Error:
A badly formatted packet or other SFTP protocol incompatibility was detected.

I believe that using an integer type that has a significantly larger capacity (such as a long) for the counter would solve this problem.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 30, 2007

@dkocher commented

Can you see the same issue with 2.8b1? The SSH library used is different in this version.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 30, 2007

2565d84 commented

Issue occurs with both 2.7.3 and 2.8b1.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 3, 2007

@dkocher commented

This looks like a server issue. The error message is given by the server.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 4, 2007

2565d84 commented

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.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 15, 2007

74743f8 commented

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'.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 15, 2008

anonymous commented

This is definitely a client bug. I was able to upload via the command line sftp client with no problem.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 29, 2008

@dkocher commented

As a workaround you might want to try SCP. Change the setting Cyberduck > Preferences > SFTP > File Transfers to SCP (SSH Secure File Transfer).

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 27, 2008

@dkocher commented

#1879 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 17, 2008

@dkocher commented

#1951 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 5, 2008

@dkocher commented

Fixed in 7f71989. Sorry this one took so long.

Loading

@cyberduck cyberduck closed this May 5, 2008
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 20, 2009

cwr commented

Looking at the descriptions, it seems likely that these two tickets describe the same bug:

Ticket #12457 (closed defect: worksforme)
"incomplete files during SFTP transfer of large directory"
opened: Jun 30, 2006
closed: May 18, 2007

Ticket #1235 (closed defect: fixed)
"Transfers larger than 2**31 (2147483648) bytes fail"
opened: Aug 30, 2007
closed: May 5, 2008

If the bug still existed in August 2007, why was the first ticket closed in May 2007 with "works for me"?

Loading

@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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants