Cyberduck Mountain Duck CLI

#7677 closed defect (worksforme)

Usability issues with segmented large uploads

Reported by: tec Owned by: dkocher
Priority: highest Milestone:
Component: cloudfiles Version: 4.4.3
Severity: blocker Keywords:
Cc: Architecture:
Platform: Windows 7

Description

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.

Change History (8)

comment:1 Changed on Dec 12, 2013 at 7:06:40 PM by dkocher

  • Resolution set to worksforme
  • Status changed from new to closed

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.

comment:3 Changed on Dec 12, 2013 at 7:58:42 PM by tec

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.

comment:4 Changed on Dec 12, 2013 at 8:10:09 PM by tec

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.

comment:5 Changed on Dec 12, 2013 at 9:15:00 PM by dkocher

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.

comment:6 Changed on Dec 12, 2013 at 9:16:57 PM by dkocher

  • Summary changed from You do not realize the problem here. to Usability issues with segmented large uploads

Duplicate for #7671.

comment:7 Changed on Dec 12, 2013 at 10:02:07 PM by tec

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.

comment:8 Changed on Dec 12, 2013 at 10:07:56 PM by dkocher

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.

Note: See TracTickets for help on using tickets.
swiss made software