Skip to main content
NetApp Knowledge Base

StorageGRID CopyObject may fail if last part of multi-part source object is 0-bytes

Views:
23
Visibility:
Public
Votes:
3
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

StorageGRID 11.7

Issue

After upgrade from StorageGRID 11.6 to 11.7 CopyObject  may fail if last part of multi-part source object is 0-bytes in size.

Aug 10 15:09:13 NODENAME ADE: |12591016 0297770069 S3RQ %CEA 2023-08-10T15:09:13.398119| NOTICE 1418 6bd4452d7c4208a6 S3RQ: EVENT_PROCESS_CREATE - connection=1691680153381874 method=PUT name=</destination/object> auth=<V4> clientIP=<ip_address>
Aug 10 15:09:13 NODENAME ADE: |12591016 0297770069 S3RQ RDDA 2023-08-10T15:09:13.720388| ERROR 0607 6bd4452d7c4208a6 S3RQ: S3 request error (error returned in body): connection=1691680153381874, Account=tennant_id, Resource=/destination/object, HTTP Status Code=500, ErrorMsg=InternalError, CustomErrorMessage={<none>}, Details={Failed to dequeue data while reading object}
 
Streaming (downloading) the object may also fail under certain circumstances, if client is not honoring content-length header.
Or if content-length header is not present in the response to client. The content-length header will not be present if client requests gzip transfer encoding, and chunked transfer-encoding being used as a result.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.