You need to enable JavaScript to run this app.
Torch Object Storage

Torch Object Storage

Copy page
Download PDF
19-MULTIPART
0019-00000110
Copy page
Download PDF
0019-00000110
Problem description​
When merging parts, the request body is not arranged in ascending order by PartNumber.​
Root cause​
The user initiated a multipart merge request, but the parts in the body were not sorted in ascending order according to PartNumber, causing the request to fail.​
Example​
You initiated the following multipart merge request:​
​
POST /objectName?uploadId=00db1329615326ddb1b901c72e2c95b8 HTTP/1.1​
Host: <Bucket name>.<TOS endpoint>​
Date: GMT Date​
Authorization: authorization xxx​
Content-Length: length​
​
{​
"Parts":[{​
"PartNumber":3, ​
"ETag":"5f0bfe97160ea0387af0311a21c2ed82"​
},​
{​
"PartNumber":1, ​
"ETag":"5f0bfe97160ea0387bf0311b21c2ed82"​
},​
{​
"PartNumber":2, ​
"ETag":"5f0bfe97160ea0397bf0311a21c2ed82"​
}]​
}​
​
In the above request, the PartNumber of the first two parts are 3 and 1 respectively, which does not meet the requirement of ascending order by PartNumber, leading to this error.​
Solution ​
Ensure that the parts in the body are arranged in ascending order by PartNumber.​
Last updated: 2026.10.08 17:59:17