incorrectly transferred (fingerprint mismatch in file contents) about unison HOT 5 CLOSED

The file contents are also used as part of the fingerprint, though you can disable this behavior (with some loss in safety -- see the manual) by setting both the fastcheck and fastercheckUNSAFE options to true.

You might try running md5 on the local and acd-mounted copies of the file and see if it agrees with diff. Otherwise, running unison with -debug=verbose (on just a single file -- the output will be large) and looking for where it's making fingerprints might give a hint.

from unison.

Thanks for your ideas. I have checked the file contents using diff and md5sum, they are identical. The debug doesn't seem to give much away about what is being fingerprinted or when. Interestingly the code suggests that the exception should indicate at least whether it was contents or metadata that differ, but that doesn't seem to be shown in the debug trace.

I have tried /c/amazon/Pictures/nas9=true and the debug is quite different, but fails because of a mismatched fingerprint. I believe this is purely based on size? The files at both ends are the same size, and the four references in the debug all match the expected size.

Any further ideas?

from unison.

the best shot for you is to override os.reasonForFingerprintMismatch to output as debug also the content of both fpdata. Diff after the function was done may not show everything.

from unison.

Thanks for the hints. For anyone else's benefit after some debugging I found the cause of the problem was on the acd_cli side, as by default it runs commands asynchronously. This can be changed using the --single-threaded option, after which unison and acd_cli work well together

from unison.

Thanks for the follow-up!

from unison.