Cannot copy file

Discuss new features and functions
mikexx
Posts: 15
Joined: 3 Nov 2016

Post by mikexx

I've got 30,00 of these errors:

Cannot copy file
"C:\DumpStack.log" to
[Pathname]\[filename].ffs_tmp".
ERROR_ACCESS_DENIED: Access is denied. [CopyFileEx]

And as many files with the ending ffs_tmp in the versioning folders.

Just counted near 40,000 files ending in ffs_tmp in the backup directory too.

I'm using 11.0
xCSxXenon
Posts: 529
Joined: 11 Jun 2019

Post by xCSxXenon

Is it the same file every time? Consider excluding it
mikexx
Posts: 15
Joined: 3 Nov 2016

Post by mikexx

No! 30,000 seperate files!!

The example I gave was bad one as being a short path and Windows 10 system file.

Unfortunately the log file only shows the first 25 of 28,931 items but I think most have a long path name.

BTW Your suggestion may take a while :-)
mikexx
Posts: 15
Joined: 3 Nov 2016

Post by mikexx

This is an example from a failed run:

16:31:59 Error Cannot copy file
"C:\Users\Mike\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\rootfs\usr\share\terminfo\h\ha8686" to
"\\DNS-323-1\Backup\C-Backup\Users\Mike\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\rootfs\usr\share\terminfo\h\ha8686~4d35.ffs_tmp".
ERROR_FILE_EXISTS: The file exists. [CopyFileEx]

While it says it exists I can use a utility like filelocator pro to find and then delete these files. But the error will appear again on the next run. As do the dangling ffs_tmp files!

You may note this line is only 178 charcters long and so should not be affected by any path limit, not that one exists in Windows 10.
xCSxXenon
Posts: 529
Joined: 11 Jun 2019

Post by xCSxXenon

What is hosting that network storage? Can you try a small set of those files to a local destination? It may be something with that
JPringle
Posts: 14
Joined: 25 Jul 2020

Post by JPringle

I have the same error for one file when syncing two HDD with FFS 11.1 under Windows 7

08:52:00 Erreur Impossible de déplacer le fichier
"F:\Linux_config\skypeforlinux\dictionaries\fr-FR-3-0~2466.ffs_tmp" vers
"F:\Linux_config\skypeforlinux\dictionaries\fr-FR-3-0.bdic".
ERROR_ALREADY_EXISTS: Impossible de créer un fichier déjà existant. [MoveFileEx]


The file to sync is fr-FR-3-0.bdic. It seems that FFS create a temporary copy before renaming it after, and it can't.
fr-FR-3-0~2466.ffs_tmp is the temporary FFS file, it doesn't exist on my HDD

Only this file has this problem, all the rest is OK
mikexx
Posts: 15
Joined: 3 Nov 2016

Post by mikexx

What is hosting that network storage? Can you try a small set of those files to a local destination? It may be something with that xCSxXenon, 11 Sep 2020, 17:13
This is a local NAS storage device, A Dlink DNS323 running ALT-F. It uses SMB 1 and 2. I have something like 2TB of data (2 million files) stored on this NAS device without any issues.
mikexx
Posts: 15
Joined: 3 Nov 2016

Post by mikexx


fr-FR-3-0~2466.ffs_tmp is the temporary FFS file, it doesn't exist on my HDD
JPringle, 14 Sep 2020, 09:58
I wonder if it has a wobbly when the file name includes a "~"?
JPringle
Posts: 14
Joined: 25 Jul 2020

Post by JPringle

fr-FR-3-0~2466.ffs_tmp is the temporary FFS file, it doesn't exist on my HDD JPringle, 14 Sep 2020, 09:58
I wonder if it has a wobbly when the file name includes a "~"? mikexx, 15 Sep 2020, 15:22
Only Zenju can say that. As I wrote, this name seems to be a temporary name fixed by FFS
xCSxXenon
Posts: 529
Joined: 11 Jun 2019

Post by xCSxXenon

Try running the sync with 'fail-safe' copying unchecked. If that doesn't work, we will want to look into permissions
User avatar
Zenju
Site Admin
Posts: 5536
Joined: 9 Dec 2007

Post by Zenju

[CopyFileEx]: Could be: viewtopic.php?t=7196
You can send me a Process Monitor trace and I can check: https://freefilesync.org/faq.php#trace
But first simplify your sync to a single file only.

[MoveFileEx]: Doesn't make any sense, unless the file "F:\Linux_config\skypeforlinux\dictionaries\fr-FR-3-0.bdic" somehow "appeared" *after* FreeFileSync comparison or the network driver of "F:\" is just buggy.