FreeFilesync 6.4 caused major corruption on a samba Networkdrive and sync.ffs_lock file cannot be removed.

[romkekats]

After upgrading to 6.4 and syncing my local project file to our samba drive many files on the Samba drive were corrupted, most likely the filesystem is corrupted, because the corrupted files are locked and cannot be removed.

[Zenju]

Is there a question? I would try to repair the filesystem then, e.g. if your server is Windows-based via right-click on drive, properties, tools, check now.

[romkekats]

No, there is no question, just wanted to report that right after updating to version 6.4 freesync corrupted the samba drive. I have been using freesync for years (i am doing a daily sync between my laptop and the samba drive), so there must have been something about this update that caused this problem. Regarding the samba drive; i am not the owner of the samba drive it is managed by our company IT department, i have no way to recover this samba drive; i do not seem to have to rights to delete the corrupted files. BTW when corruption occurs the freesync Lock file on the samba drive is also corrupted and is no longer deletable. (the samba drive is a RAID based NAS)
I do have a question: I reverted back to version 6.3 just in case. Is it safe to use the latest version? or should i wait for the next version before updating?

[Zenju]

In short, correlation does not imply causation (CDNIC): It's practically impossible that FFS could be the cause for data corruption, simply due to the fact that it does not copy any data; but Windows does. FFS just tells Windows (via its API) to copy the files. So one could think that it's a Windows problem then. But that's very unlikely, again CDNIC. More likely there is either some technical problem with your hard drive or your file system got corrupted somehow, but at least the file system can be repaired.