Failing after exception: File too big for renaming

English Support for Syncovery on Windows.
Post Reply
mrtns
Posts: 2
Joined: Mon Mar 22, 2021 11:12 pm

Failing after exception: File too big for renaming

Post by mrtns »

Hi!

I'm running Syncovery to snapshot the files inside a Shared Drive on Google Drive onto an S3 Bucket, however I'm running into an error when a specific new file is to be uploaded.

Code: Select all

Failing after exception: File too big for renaming, Retry Number: 0
19:07:24.211 Error renaming S3://<REDACTED>.d20210320-u214236.rar to S3://<REDACTED>.d20210320-u214236.rar: File too big for renaming

Errors / Access problems with 1 File:

\<REDACTED>.rar (File too big for renaming of type ERunException at 0000000001DB3DA8)
The file in question is about 12GB and does not exist on the other side.

Curiously enough, I've synchronized bigger files, but it seems this one in particular causes trouble.

Logs below:

Code: Select all

Syncovery v9.32, build 174 (64-bit)

Licensed to: <REDACTED>
Running on : <REDACTED>
Running as : <REDACTED>  (not Admin)
System Info: Microsoft Windows 10 Pro Build 19042
Using Backup Privilege

Log for profile <REDACTED>, started at 19:07:18 on 2021-03-22

LEFT: ext://<REDACTED> (ID:<REDACTED>)
RIGHT: S3://<REDACTED>

The profile has been started manually the background.

Previous run was at 2021-03-22 18:47:26: 0 copied, Errors with 1 File(s)


Using OpenSSL 1.1.1i  8 Dec 2020: libssl-1_1-x64.dll, libcrypto-1_1-x64.dll

TLS Certificate verified successfully.
This server does not support empty folders.
Copying Direction : Left To Right
Exact Mirror Mode is being used.

Scanning Folders Started At 2021-03-22 19:07:18
2021-03-22 19:07:18 Google Drive: Refreshing Access Tokens
2021-03-22 19:07:18 Google Drive: 2021-03-22 19:07:18 TSynGDrive.RefreshAccess.
2021-03-22 19:07:18 Google Drive: Refreshing Access
2021-03-22 19:07:18 Google Drive: New Access Token: <REDACTED>, Different From Previous=Y
2021-03-22 19:07:18 Google Drive: Connect Successful
Getting Amazon S3 Listing (splitting after 2000000 entries)
S3 Listing Downloading Time: 3.29 seconds for 5 HTTP requests
S3 Listing Processing Time : 0.11 seconds for 4147 directory entries
19:07:22.71: Opening Database: C:\ProgramData\Syncovery\Database\<REDACTED>[google]v3.syncfdb
19:07:22.74: Connecting With Database
19:07:22.123: Database Connected
19:07:22.127: Database Opening Complete
Using Cloud Cache Database: C:\ProgramData\Syncovery\Database\<REDACTED>[google]v3.syncfdb (283 Folders, 4431 Entries, DB size: 3,920 kB)
Loading tree from database.

Loading items from database took 0.16 seconds, of which 0.00 for saving memory (0 invocations), of which 0.00 for updating last usage counts (0 invocations), 0.00 for taking subtrees offline (0 invocations).
Also Used 0.00 seconds for putting subtrees back online (0 invocations).
Total Item Count Within Base Folder: 4431, Items With ID: 4431, Offline Item Count: 0

Getting changes history for google from checkpoint 9625
2021-03-22 19:07:22 Getting Changes from Google Drive, using JSON Cache file C:\ProgramData\Syncovery\Database\<REDACTED>[google]9625.json
2021-03-22 19:07:22 Getting Changes from Google Drive, Part 1
Confirmed no more changes to process.
2021-03-22 19:07:22: Received 1 pages of changes.
Scanning folders took 00:00:00 (hh:mm:ss)
19:07:22 Reading left-hand side directly: 
Getting changes history for google from checkpoint 9625
2021-03-22 19:07:22 Getting Changes from Google Drive, using JSON Cache file C:\ProgramData\Syncovery\Database\<REDACTED>[google]9625.json
2021-03-22 19:07:22 Getting Changes from Google Drive, Part 1
Confirmed no more changes to process.
2021-03-22 19:07:22: Received 1 pages of changes.

Free Space on right side:  Not checked, needed:    0 Bytes

Failing after exception: File too big for renaming, Retry Number: 0
19:07:24.211 Error renaming S3://<REDACTED>.d20210320-u214236.rar to S3://<REDACTED>.d20210320-u214236.rar: File too big for renaming

Errors / Access problems with 1 File:

\<REDACTED>.rar (File too big for renaming of type ERunException at 0000000001DB3DA8)

Closing database C:\ProgramData\Syncovery\Database\<REDACTED>[google]v3.syncfdb (283 Folders, 4431 Entries, DB size: 3,920 kB)
19:07:24.273 Database closed

SUMMARY
------------------------------------------------------------------
Short Results: 0 copied, Errors with 1 File(s)
Operation completed at 19:07:24 on 2021-03-22
Total duration: 00:00:06

Errors with 1 File(s).



Local time zone offset: -4.0 hours.
Internet protocol timeout: 60 seconds
Max. Internet protocol retries: 2

------------------------------------------------------------------

Profile Settings From C:\ProgramData\Syncovery\Syncovery.ini

[General]
Name=<REDACTED>
LastModified=2021-03-22 19:06:49
LeftPath=ext://<REDACTED> (ID:<REDACTED>)
RightPath=S3://<REDACTED>
LeftToRight=Yes

[Comparison]
MaxSecondsDiff=600
IgnoreExactHourDifferences=No
IgnoreSeconds=Yes
SizeConflictAction=scaCopy

[Exact Mirror Config]
ExactMirrorDeletes=Yes
ExactMirrorReplacesNewerFiles=Yes

[Folders]
CreateEmptyFolders=No
RemoveEmptyFolders=Yes

[Internet]
LeftFTPSettings=Ext:ExtProt=Google Drive,Flags=UTF8+ReplaceChars+UTC+DetectTimezone+ReplaceAutomatic,"Proxy=no",Lib=0
LeftExtendedProtocolName=Google Drive
RightFTPSettings=S3:Flags=UTF8+ReplaceChars+UTC+DetectTimezone+ReplaceAutomatic,"Proxy=no",Public=N,TLS=Y,StorageClass=5,RecursLst=Y

[Safety->Unattended]
UnattendedDeleteFiles=Yes
UnattendedDeleteMaxPercent=20
UnattendedReplaceMaxPercent=20

[Schedule]
ScheduledNormally=Yes
RepeatAfter=Yes
OrigTimeOfDay=00:00:00

[Schedule->More]
RunUponStartUp=Yes

[Schedule->Weekdays and Time Window]
Weekdays=Mtwtfss

[Versioning]
FilenameEncoding=Yes


------------------------------------------------------------------


Default System Codepage: 1252

------------------------------------------------------------------


Email Notification Settings:
Profile was started manually, and email is turned ON for manual runs.
Email Should Be Sent: Yes
Reason: Error Has Occurred

Email Delivery Settings:
Sender Name: Syncovery
Sender Email:<REDACTED>
SMTP Server: <REDACTED>
SMTP Port  : 465

Configuration path for notication settings:
C:\ProgramData\Syncovery\Syncovery.ini


------------------------------------------------------------------



The Notification Email is now being prepared.
Recipients : <REDACTED>
          -> <REDACTED>
Connecting to <REDACTED>, port 465
Connection successful.
Sending Email.
Email sent successfully.
SMTP Result: 250 2.0.0 OK  <REDACTED>


------------------------------------------------------------------

mrtns
Posts: 2
Joined: Mon Mar 22, 2021 11:12 pm

Re: Failing after exception: File too big for renaming

Post by mrtns »

Ok, I solved the issue, however I'm unsure to what caused it.

Turns out I had a file with the exact same name (name + type) on the root folder in S3. This file was not present in the Left side, and should have been deleted as configured.

I manually went ahead and nuked it out of S3 and rerun the profile. It is now uploading just fine.

If you run into this issue, make sure the Right side doesn't have some orphaned file with the same name.

tobias
Posts: 552
Joined: Tue Mar 31, 2020 7:37 pm

Re: Failing after exception: File too big for renaming

Post by tobias »

Hello,
thanks! I think Syncovery wanted to rename the existing file, or move it into a "folder for deleted files", but couldn't because the size limit for renames is 5 GB. I will check if the Amazon S3 API actually does support renaming larger files and try to implement it.

Post Reply