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

Segmented downloads with multiple connections per file causes transfers to fail and exceed file size on server #13374

Closed
lpagani91 opened this issue May 10, 2022 · 16 comments · Fixed by #14839
Assignees
Labels
b2 Backblaze B2 Protocol Implementation core ftp FTP Protocol Implementation sftp SFTP Protocol Implementation
Milestone

Comments

@lpagani91
Copy link

Running Version 8.3.3 (37544), I tried to download a 39GB file on my computer. With a ~15 MB/s transfer rate, it indicated about 55 min. to download the file (accelarating, slowing down, etc...). I returned 4 hours later and it was still running with a file being 4.5 times the size of the original file
Capture d’écran 2022-05-10 à 17 34 31
I killed it and tried again from home tonight. Same result. It reached 100% and went on downloading. I stopped it at 101%.
I am downloading it via good old ftp now but it is 3 times slower so only at 57% at the moment.
Is it a problem with cyberduck or with the file or both ?

@lpagani91
Copy link
Author

lpagani91 commented May 10, 2022

The download with old ftp file was fine. It was only much longer. So the problem is with Cyberduck only :
150 Opening BINARY mode data connection for m9501_109.tar (39285760000 bytes).
100% |***********************************| 37465 MiB 5.46 MiB/s 00:00 ETA
226 Transfer complete.
39285760000 bytes received in 1:54:14 (5.46 MiB/s)

@arex388
Copy link

arex388 commented May 19, 2022

I can also confirm this on 8.3.3 when downloading from an S3 bucket. I was trying to download a 134.7GB file, and the download continued even though the estimated time had long since passed. After waiting for two hours just in case it was real, I stopped the download and it said that it had downloaded 184.2GB. It would appear that Cyberduck has an issue with large files. Perhaps its not "realizing" the file has finished and is repeating the ending segment(s)?

@networkneil
Copy link

I was having this issue too. I was trying to upload a folder of size 130GB and the copy speed starts of good and drops to almost zero and its failing constantly. Then I had to resort to AWS CLI.

@networkneil
Copy link

I was having this issue too. I was trying to upload a folder of size 130GB and the copy speed starts of good and drops to almost zero and its failing constantly. Then I had to resort to AWS CLI.

Edit:
sorry forgot to mention, I was doing an upload to s3 bucket.

@demodit
Copy link

demodit commented May 22, 2022

Downloads of big files from FTP server by FTP-SSL do not work since months (earlier it did work). Now I encounter also infinite downloading.

@lpagani91
Copy link
Author

lpagani91 commented May 22, 2022 via email

@demodit
Copy link

demodit commented May 22, 2022

I mean downloads by Cyberduck.

@spacepluk
Copy link

This is still happening

@krilupo
Copy link

krilupo commented Oct 3, 2022

Hi guys, issue still present - also on my end.
Trying to download a 4.9GB file which results in an endless loop ...
Please fix this.
Thanks

@LucasJanin
Copy link

Same issue on my side with version 8.4.4.
Switching temporarily on Filezilla

@dkocher
Copy link
Contributor

dkocher commented Oct 10, 2022

@lpagani91 Try to uncheck Preferencers → Transfers → Downloads → Segmented downloads with multiple connections per file to reduce the load on the server.

@LucasJanin
Copy link

@dkocher Yes this fixes the infinite downloading!!
Thanks for the tips!
Hoping the problem gets resolved soon.

@krilupo
Copy link

krilupo commented Oct 11, 2022 via email

@dkocher dkocher added the core label Oct 24, 2022
@dkocher dkocher self-assigned this Oct 24, 2022
@dkocher dkocher added the ftp FTP Protocol Implementation label Oct 24, 2022
@dkocher dkocher changed the title infinite downloading Segmented downloads with multiple connections per file causes transfers to fail and exceed file size on server Oct 24, 2022
@LucasJanin
Copy link

FYI, the problem isn't present over SFTP

@dkocher dkocher added this to the 8.6.2 milestone Jun 21, 2023
@dkocher dkocher linked a pull request Jun 22, 2023 that will close this issue
dkocher added a commit that referenced this issue Jun 27, 2023
Review transfer status with retry after failure
@HKdAlex
Copy link

HKdAlex commented Jul 25, 2023

I experience the same problem when downloading a folder from an S3 server.

@dkocher
Copy link
Contributor

dkocher commented Jul 25, 2023

I experience the same problem when downloading a folder from an S3 server.

This should be resolved in the current snapshot build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
b2 Backblaze B2 Protocol Implementation core ftp FTP Protocol Implementation sftp SFTP Protocol Implementation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants