juicefs sync failed with 'multipart: NoSuchUpload' #3965
Replies: 5 comments
-
This should be the problem of the object storage provider. Please contact the supplier first to check why the |
Beta Was this translation helpful? Give feedback.
-
@lixiaofengfeng Can you reproduce this issue? |
Beta Was this translation helpful? Give feedback.
-
yes. I created a gateway through command 'juicefs gateway ......' and there is an endpoint that have access to this gateway. Every command is like 'juicefs sync s3://ak:sk@bucketname.gateway_endpoint/data_path s3://......' . |
Beta Was this translation helpful? Give feedback.
-
Based the content discussed offline, the issue came from BOS (claimed to be compatible with S3, but may have some issues). We can't reproduce this issue with BOS using the BOS SDK, or with other S3 compatible storage providers. |
Beta Was this translation helpful? Give feedback.
-
What happened:
Error occured when I run command 'juicefs sync --check-new' and it returns as below:
2023/08/02 06:18:04.240278 juicefs[1003] : Failed to copy data of in 13m16.963721297s: multipart: NoSuchUpload: The specified multipart upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.
What you expected to happen:
The file should be transferred successfully.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
The file size is about 12.55GB.
Environment:
juicefs --version
) or Hadoop Java SDK version:cat /etc/os-release
):uname -a
):Beta Was this translation helpful? Give feedback.
All reactions