Failing after exception: File too big for renaming

[Jean-Michel]

hello,

I'm trying to get 112 files copied from an AWS S3 bucket to another S3 bucket
All files fails with the below status:

Code: Select all

Failing after exception: File too big for renaming, Retry Number: 0
Exception File too big for renaming at 000000000112C164.
Filename: S3://redacted-source-bucket-name/FULLSHOWMA0718.mxf
Checkpoints: HTX

I tried "Copy" and "StartTracking" but both end with the same error
The job is meant to be run only once, so no schedule or smart monitoring

It looks strange as Syncovery seems to try to rename the source file.

Any hint on why it would do that ?

Thanks

[tobias]

Hello,
thanks for the report! Syncovery tries to copy the file on the server side rather than downloading and re-uploading. The error message is wrong, it's not trying to rename it. For some reason the size is too big for this server side copy, which is surprising because the limits are well known and Syncovery respects them, copying large files in parts.

A few questions:
How big are the files?
Which Syncovery version do you have?
Could you possibly send a complete log file to support@syncovery.com?

As a quick workaround, maybe you can create two separate profiles, one that downloads to a local folder and another one that uploads to the destination bucket. Other than that I am absolutely interested in fixing the problem.

[Jean-Michel]

Hi Tobias

Thanks for jumping in quickly
- Files are from 3GB up to 89GB
- Version 10.11.9
- Running as a docker container in AWS fargate: 4 vCPU, 8 GB RAM and 200GB local storage

We have another profile running fine with files of similar size but from a Google Storage bucket to S3
This one is S3 to S3
The 2 buckets are in the same region (us-east-1) although the source bucket do not belongs to our account but to a customer
But our root AWS account has been granted the proper rights, no problems accessing bucket and downloading files with other tools (WinSCP, Cyberduck, ...)

I'll send you the logs

Thanks