OS: Windows 10
I inadvertendly happen to sync the content of a folder containing two subfolders named "NATALE 2013" and "Natale 2013" to a target folder.
Each folder contained exactly the same files.
Attempting to mirror sync, I get the error "Cannot rename file ..." (referring to a temp filename (I do not have the exact error message).
I first tried to delete the target subfolder but the problem continued.
The problem solved as soon as I delete the source subfolder namerd "NATALE 2013".
This suggest that FreeFileSync does not take into account the case of the name of a target folder when generates the temp filename.
Cannot rename file
- Posts: 13
- Joined: 16 Aug 2024
-
- Posts: 2978
- Joined: 22 Aug 2012
Correct.
Just like in Windows, file- and folder-names are not case sensitive in FreeFileSync (FFS).
So, "NATALE 2013" and "Natale 2013" are considered to be one and the same.
Just like in Windows, file- and folder-names are not case sensitive in FreeFileSync (FFS).
So, "NATALE 2013" and "Natale 2013" are considered to be one and the same.
-
- Site Admin
- Posts: 7523
- Joined: 9 Dec 2007
No, the opposite is true, you're getting an error *because* FFS carefully considers case and does not consider them to be the same. Your target file system however is a different story.
- Posts: 323
- Joined: 13 Apr 2017
Please tell us what file system are the source and the destination.
In Windows the default behavior is case-insensitive, but, from Windows 10 1803 up, you can use fsutil to enable a per-directory case-sensitivity.
Did you enabled this attribute in the folder containing the two mentioned source folders?
In Windows the default behavior is case-insensitive, but, from Windows 10 1803 up, you can use fsutil to enable a per-directory case-sensitivity.
Did you enabled this attribute in the folder containing the two mentioned source folders?
