Yesterday before going to sleep I decided to re-hash my syncthing folders. I use this to detect bit rot and to make sure some super large files (containers) are bit-by-bit correctly stored. Usually i never have any sync conflicts after doing this. But I since all my syncthing devices are on .48 I decided to enable large blocks on the device I was re-hashing everything throughout the night. After waking up, like all files larger than 300 MB and those up to 30 GB were copied to my corresponding server with sync-conflict in it. Only one folder on my server didn’t have one conflict - the one and single folder I enabled Large Blocks some weeks ago when I let the machine re-hash everything.
It look for me like there is a problem with Large Blocks if the option is disabled on one side. I checked the files on my both PCs with Total Commander (bit-by-bit). All are absolutely the same. Either checked between the sync conflicts or the original files. That means that there is some kind of hash check mistake? Or the other side does not correctly use the large blocks since it doesn’t have hashed large blocks yet? Do I have to enable large blocks on all devices and let everything rehash again? There is no warning that the other side doesnt have large blocks yet or has to rescan itself the files because the starting side sends large blocks only?! Im confused :).