FreeFileSync Forum

A list of the checksum of all the files copied / synchronized in the database could allow FFS to recheck the integrity of the pairs of unmodified files whose checksum differs during future synchronizations. And also to be able to ...

... file would overwrite a healthy backup. In short, if between 2 files (source and destination) never modified (seen by date) one of them had a checksum different from the first or last synchronization, it would be useful for FFS to be able to detect it and warn of a possible corruption by preferring ...

... During the first synchronization between two disks with content comparison (bit by bit), do the databases thus produced on each side contain the checksum of each file for a later comparison ? Cordially

It obviously differs per platform, but for Windows see e.g. here.

Thanks for your reply, Plerry. The way I see it, adding validation functionality would only improve the quality of what FFS is doing. Rather than just copying files and make sure they appear updated in two locations, one could argue that the users primary concern and interest is in the contents of t...

Your vote is for using chechsums for validation, which is something different than using chechsums to determine which files need to be copied, as was proposed by TS raven. In either case, the first part of my my earlier reply still holds. A for your (Fossie's) proposal: as FFS only runs in one locat...

... like to add a vote for this to be implemented. It would be a great way to allow for data scrubbing. Every time a file is updated, recalculate the checksum. Schedule periodically verification of checksums. If a mismatch is found, we know the file has been corrupted, and should be given the option ...

Hello, I came to this post looking for exactly the same thing. I really like FFS but I too think the lack of checksums is a security hazard, especially for Linux binaries. The other OS's have signed installers that provide some mitigation, and even more so from virus scanning ...

Performing compare between 2 directories: left D:, right T:. - The file "Google Drive/desktop.ini" is on both sides and has same checksum, but has different timestamps. - Comparison (F6): File time and size, don't include symbolic links, don't ignore time shift. - Synchronization: ...

... the destination file. Some parameter should be available like filename. An other idea is hashing. Using the pipe to hash the files than creating checksum files. "sha3sum -o $filename$.sha3" will result a inline hash generation for each file and as output. demo-file.avi and demo-file.avi.sha3 ...

I have performed checksum on a bunch of photos of two subsequent backups and the files were exactly the same.
If I can provide any log, please let me know how to do and where I can collect them.

... be grateful if someone could explain what is going on and maybe from there I can get a remedy. (1) Before doing the Mirror sync I construct an MD5 checksums file so that I can check the sync went okay after the sync is completed. (2a) I perform the sync and then check the result with the checksums ...

... its final destination successfully?" You may be comparing cashed data, instead of data as read from disk. Several users have suggested to use checksums. However, the use of checksums only makes sense if the checksum check is run locally to where the files are stored. If you first need to download ...

... processing to compare). is there a way of comparing the original and copied files during the synchronization process, on the fly, via hash (file checksum) or whatever? Thanks in Advance

... compare the mentioned two files? The filenames are different. FFS is primarily a file-sync tool, and is not a duplicate finder.! @necrolord : A checksum may be useful in identifying duplicates. But finding differently named duplicates is beyond the scope of FFS.

It can be solved with a checksum management. Not sure if author will add this....

... if a such type of a mismatch was found too late (after several years of holding HDD on a bookshelf). So, to make FFS robust enough you have to add checksum management. Checksums must be stored somewhere and must be refreshed with every internal data compare act. That's only feature that FFS lack ...

... as expected. Does it work? I understand where is the problem, but I do not even understand why this error occurs! I tried latest version 1.14 md5 checksum 8094f2b903ab056cc1a9c8ff39250b35 with same result! Everytime i reach same results Job Name = D:\Desktop\SyncSettings GetLogFile return value ...

... suggested and discussed before. An FFS sync runs only on one machine, e.g. the machine of your left base location. In said case, determining the checksums of files in the left base location (and subtree) could be quick. However, for determining the checksum of the files (and subtree) in the right, ...

That is, I specify in the program the generated checksum file for Destenation or Source, based on it the program determines what to copy. Why this is important: at this stage, when synchronizing over a network (ftp or Samba), you actually have to ...

Interesting. Your 32-bit version of sigcheck fails to verify the signature, while the 64-bit one succeeds.

In my test, the 32-bit version of sigcheck also succeeds to verify. FreeFileSync_XP.exe is also a 32-bit executable.

7dea96ea31b15d099a343a47c2d48e21 is the correct checksum.

... not "verified" and do not show a "publisher". Maybe the installer really *is* corrupt due to a download error? Can you post a checksum of the installer (whatever you can generate).

... and FreeFileSync end up syncing gigabytes of files even though the photos are the exact same match. Perhaps FreeFileSync should also generate checksum for either "source" or "destination" and compare the checksum first to see if the file really changed. This would be useful ...

... ######################################################################## 100.0% ==> Verifying checksum for Cask freefilesync ==> Note: running "brew update" may fix sha256 checksum errors Error: sha256 mismatch Expected: aaa1dd1e2dfcc39bf4673d8280cc6561ee8dc9921c4deb926ed336dd5aa1d57b ...

... apt-get for windows) that automatically grabs the windows install URL and if there is a version change, builds a new package and calculates the checksum to verify before installing. I'm hoping you guys would be willing to do a bit of work or work with me about making it a bit easier to know ...

... guessing is why they don't seem to have the problem. Just to be clear- verification set to ON will verify that the final copied file has the same checksum as the original? It's a bit-wise comparison, so this implies the same checksum. Again, I wouldn't rely on the checksum to keep the data safe, ...

... way more people than it seems to affect currently. Just to be clear- verification set to ON will verify that the final copied file has the same checksum as the original? It's a bit-wise comparison, so this implies the same checksum. Again, I wouldn't rely on the checksum to keep the data safe, ...

... removal policy, etc) and I'm hoping for the best. Just to be clear- verification set to ON will verify that the final copied file has the same checksum as the original? What is it using, if I may ask? CRC? Seems too fast to be MD5. I'm under the impression that MD5 would probably be overkill ...

... now see it has been happening for years under my nose. I just copied a directory of about 6 hours worth of unedited video (75GB). Verified with checksum generator, and sure enough one of the 7 mov files has a mismatched MD5. In the mean time, Teracopy and others with their own routines for copying ...

... realize it is happening, as Windows does not report any errors, files are the correct size. The only way to tell something went wrong is using a checksum to verify (or in my case, when editing a video and realizing frames are missing). But knowing that it will happen to one out of 5 files over ...