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

Usability issues with segmented large uploads #7677

Closed
cyberduck opened this issue Dec 12, 2013 · 8 comments
Closed

Usability issues with segmented large uploads #7677

cyberduck opened this issue Dec 12, 2013 · 8 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Dec 12, 2013

b7e3126 created the issue

When loading a 4 gb file it breaks into hundreds of 5mg files, in a single Rackspace file, becoming are hundreds of separate chunks
that cannot be put back together. Consequently, no file over 2gb can be loaded using Cyberduck.
Any file over 2gb is unusable because it is segmented into 5 mg little blocks in Rackspace.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 12, 2013

@dkocher commented

There is also a manifest file uploaded with the original filename that references the segments. Cloudfiles will return the full file when linking to this this manifest file.

Loading

@cyberduck cyberduck closed this Dec 12, 2013
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 12, 2013

@dkocher commented

Refer to the Cloud Files FAQ.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 12, 2013

b7e3126 commented

You need to let Rackspace know they need to train their tech support on this right away!! They do not have a clue about this Cyberduck configuration problem of manifesting a file over 2gb. They are losing customers in droves and promising they will have their file loader up some time soon. Maybe months from now. But this is a serious problem. We have switched to another lessor company then Rackspace because it caused unworkable problems for us.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 12, 2013

b7e3126 commented

This manifest file is to complicated to use... it needs to show one file to load.... not a lead manifest file. You need to reconfigure it to operate the way it was before this 'upgrade'.... the upgrade of breaking down files makes it to clumsy for users.
Me and many other Cyberduck fans are out until you remedy the problem you have made.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 12, 2013

@dkocher commented

You can disable the use of segemented uploads for files smaller than 5GB with the hidden setting openstack.upload.largeobject set to false.

We have opted to make this the default for files larger than 2GB as it allows to resume an interrupted file transfer. We have announced support for large uploads on our blog in Large Uploads for OpenStack Swift.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 12, 2013

@dkocher commented

Duplicate for #7671.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 12, 2013

b7e3126 commented

Your kidding right? That response may seem very simple to a programmer. But I am not. Please provide a button to select if I want to choose the 5mg as a default to assure restarting loading. Otherwise please have it default to constant streaming. It is a big mistake to default to segmented loading without making it much easier to recombine the whole file.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 12, 2013

@dkocher commented

You do never ever have to recombine the whole file manually. This is done automatically by the server when the file is requested. Internally all segements stored in .file-segments/ are referenced by the manifest file uploaded. But when downloading, this is handled transparently and you don't need to know anything about segmented files.

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