search

astrada / google-drive-ocamlfuse

FUSE filesystem over Google Drive
https://astrada.github.io/google-drive-ocamlfuse/
MIT License
5.52k stars 351 forks source link

Data Transfer Verification #735

Open dvhirst opened 2 years ago

dvhirst commented 2 years ago

Hello, Thanks for writing and maintaining this very useful file system app. In general, it has worked well for me. I am using it to transfer backup data from an AWS virtual server to a Google Drive account/folder; so far, it is working as expected. Occasionally, a transfer will have an error and not all the files in a run get transferred. I'm looking for suggestions about ways to verify that all the expected files have been transferred and are in the expected target folder. Advice welcomed. My initial thought is; after the transfer is completed, run an MD5 checksum on the source and destination folders, and compare the results. If they match, the data are good. I'll try that out and report results.

astrada commented 2 years ago

My initial thought is; after the transfer is completed, run an MD5 checksum on the source and destination folders, and compare the results. If they match, the data are good.

Yes, I think it should work.

I'll try that out and report results.

Thanks!

rautamiekka commented 2 years ago

If MD5 will be used, it's borderline the same as no check at all.

ghost commented 2 years ago

If MD5 will be used, it's borderline the same as no check at all.

@rautamiekka Could you explain why you feel that this is the same as no check? What is the issue with MD5?

rautamiekka commented 2 years ago

If MD5 will be used, it's borderline the same as no check at all.

@rautamiekka Could you explain why you feel that this is the same as no check? What is the issue with MD5?

All the collisions, of course. I don't expect that to matter, though, even when the one introducing it has his files corrupted or deleted.