FFS erroneously thinks file exists on one side only

[kydar]

(Using v11.29 64-bit donation edition)

I ran a comparison on two folders that were previously synced with another app (Synchredible, if it makes a difference). FFS showed lots of files that it said existed only on one side, but when I check with a file browser, they exist (i.e., are synced correctly) on both sides.

Just to see what would happen, I selected a subset of them and ran a Mirror anyway. As might be expected, FFS errored with "Cannot move file path1:\blah\blah\blah to path2:\blah\blah\blah. ERROR_ALREADY_EXISTS: Cannot create file when that file already exists. [MoveFileEx]"

The only similarity I can find among the failed files is that they all have somewhat long names. The total path including filename is not greater than 260 characters, and no subunit of the path/filename is more than about 50 characters. This is well within Windows 10's specs (and I do have 32,767 long filename support turned on anyway) but like I said, it's the only similarity that I can spot offhand.

Any hints?
Thx

[xCSxXenon]

Case-sensitive file system vs one that isn't?

[kydar]

Case-sensitive file system vs one that isn't?

You, sir, are a genius. I, on the other hand, am a stunade. That was precisely the problem. The source dir was created by a Linux system and had several subfolders that comprised the same letters in their names, only one was all lower case and one was mixed case. Linux, of course, considers these completely separate folders, but Windows (or more accurately, NTFS) considers them the same so it choked when asked to compare or copy them.

My solution was to just RAR up the entire folder and all subfolders so FFS just sees a single archive file and happily copies it.

Thank you so much!

[xCSxXenon]

:D

[I stole your coconut]

Case-sensitive file system vs one that isn't?

You, sir, are a genius. I, on the other hand, am a stunade. That was precisely the problem. The source dir was created by a Linux system and had several subfolders that comprised the same letters in their names, only one was all lower case and one was mixed case. Linux, of course, considers these completely separate folders, but Windows (or more accurately, NTFS) considers them the same so it choked when asked to compare or copy them.

My solution was to just RAR up the entire folder and all subfolders so FFS just sees a single archive file and happily copies it.

Thank you so much!

Whats the solution here? I am having the same problem

[xCSxXenon]

"My solution was to just RAR up the entire folder and all subfolders so FFS just sees a single archive file and happily copies it"