Bug with copying files with : in names

Get help for specific problems
Posts: 2
Joined: 17 Mar 2007

ski98033

Hi,

When FFS tries to copy over a file like 'Screenshot - 03302015 - 01:37:48 PM.png', I get these errors:

version 6.15:
[07:16:16 AM] Info: Creating file "/fs/Staff/ckacoroski/Documents/Backup/CURRENT/.local/share/Trash/files/Screenshot - 03302015 - 01:37:48 PM.png"
[07:16:16 AM] Error: Cannot move file
"/fs/Staff/ckacoroski/Documents/Backup/CURRENT/.local/share/Trash/files/Screenshot - 03302015 - 01:37:48 PM.png.ffs_tmp" to
"/fs/Staff/ckacoroski/Documents/Backup/CURRENT/.local/share/Trash/files/Screenshot - 03302015 - 01:37:48 PM.png".
Error Code 20: Not a directory (rename)

version 6.12:
[07:17:10 AM] Info: Creating file "/fs/Staff/ckacoroski/Documents/Backup/CURRENT/.local/share/Trash/files/Screenshot - 03302015 - 01:37:48 PM.png"
[07:17:10 AM] Error: Cannot write modification time of "/fs/Staff/ckacoroski/Documents/Backup/CURRENT/.local/share/Trash/files/Screenshot - 03302015 - 01:37:48 PM.png.ffs_tmp".
Error Code 2: No such file or directory (utimes)

In both cases, the file created on disk is: 'Screenshot - 03302015 - 01'

I am running FFS on Linux Mint Debian Edition. Let me know if there is any other information I can provide to help you fix this problem.

cheers,

ski
User avatar
Site Admin
Posts: 7211
Joined: 9 Dec 2007

Zenju

> version 6.15:

Not sure why "rename" would fail with ENOTDIR due to the existence of colon characters on Linux, but it's not a bug in FreeFilesync and a limitation of this Posix API.
As a workaround, disabling global settings "fail-safe file copy" should make it work, although that's a bad idea in general.