FreeFileSync Forum

Hello and Merry Christmas :)

You might have hardlinked files on your main flash drive. In case you aren't aware of the concept of hardlinks, that means that there are multiple file system entries (=files) pointing to the same memory location. You would have the same content in different folders ...

Thanks!

Uh oh.
I analyzed the file list. Basically, I was doing a one way sync from lhs to rhs with lots of moves, some new and some deleted. Everything else is insignificant or not present.
Stats:
create -> 71 GB
move from -> 649 GB
move to -> 649 GB
delete -> 210 GB
This lets me think the move detection ...

I don't know how to attach images here, so I'll just leave this note here:
I think there is something wrong with the calculation of one or more of the sync parameters.

I have a sync job running and this is what the status window shows:
900,35%
Verbleibende Elemente: 52.058 (-566 GB ...

> FreeFileSync 5.17 Changelog
> [...]
> Show moved files in same category as updated files

Awesome, not exactly what I wanted but it solves my problem!

Thank you for this explanation. I agree, symlinks can produce complex situations. The issue above already arises if the user decides to delete file.txt and you can just let it happen. You never know which file is target of a symlink, for sure if the symlink is outside the sync directory. So I'm not ...

Okay, that is not what I experienced, at least not with 5.18.
Situation:
Folder 1: two files (hardlinked to each other)
Folder 2: same two files (doesn't matter if they're hardlinked to each other, too)
If i move one of the two hardlinked files, move detection works. If I move both of the files ...

Do you have any idea what I could do to analyze the present situation to help with a test case?

I just noticed that under some circumstances files that have hardlinks and get moved slip through FreeFileSyncs 'moved file' detection. Instead of moving them on the target directory, they get deleted and copied again.
This happened on a large sync job and I didn't manage to reproduce this in a ...

I'm aware of the fact that I posted this in the wrong section. This should have gone into Open Discussion. But nevertheless, doesn't anyone have any thoughts about this?

I'm very cautious about my work files, so I use to do a quick review of each sync process. Sometimes I move a lot of files and only delete a few. While moved files usually aren't much of a problem, deleted files could have been deleted by accident. I find it hard to review this at the moment because ...

I can't tell you what the colors are about, but the percentage tells you how much space every folder consumes (that is all files in this folder and in it's subfolders) in comparison to other folders of the same level. For example, the 40% and 60% folders tell you that of the space that the parent ...

Source is NTFS, destination is FAT32.
AFAIR this error occurs every time but the first time syncing. I suspect FFS
detecting an identical file in both locations with different timestamps. When
it tries to copy timestamps from one file to this other, this procedure fails.
I will send you ...

Hi.
I'm getting Windows Error 87 when trying to sync files that have no
modification date. (Those sometimes show up as 1970-something and sometimes
the date is just empty) Those files are rare and I don't know how to create
them. If it helps, I could send one of them. For more information I need to ...