[Cyberduck-trac] [Cyberduck] #9636: Wrong size of large file manifest using swift

Cyberduck trac at trac.cyberduck.io
Thu Jul 28 13:04:50 UTC 2016

#9636: Wrong size of large file manifest using swift
 Reporter:  selectel                   |         Owner:
     Type:  defect                     |        Status:  closed
 Priority:  normal                     |     Milestone:  5.1
Component:  openstack                  |       Version:  5.0.9
 Severity:  normal                     |    Resolution:  worksforme
 Keywords:  manifest swift large file  |  Architecture:  Intel
 Platform:                             |
Changes (by dkocher):

 * status:  new => closed
 * resolution:   => worksforme
 * milestone:   => 5.1


 To me everything looks correct as described in [http://docs.openstack.org
 /admin-guide/objectstorage_large-objects.html Large object support].

 > A manifest object links the segment objects into one logical large
 object. When you download a manifest object, Object Storage concatenates
 and returns the contents of the segment objects in the response body of
 the request. The manifest object types are:

 You will find the parts with `path` and `size_bytes` in the manifest files
 referenced. The manifest file itself is a JSON file referencing the large
 upload parts. Swift will transparently give you back the full content when
 requesting the manifest file with a `GET` request (Or as you mention
 yourself when doing a `HEAD`request you get the `20G` object size

Ticket URL: <https://trac.cyberduck.io/ticket/9636#comment:1>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows

More information about the Cyberduck-trac mailing list