Corrupted file on either side

[y-lohse]

When I start the desktop app, the sync fails with the following error message ( in a console ):

(node:12596) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 9): Error: File is corrupt on either side (md5sum matches but size does not)

I don't know how to get more info, and this prevents me from syncing at all.

Let me know if I can provide more details.

---

Originally posted by @flo-dhalluin here

[taratatach]

Hi @flo-dhalluin,

I'm sorry for the delay. This error means that your file has been corrupted on your computer or your Cozy. We've seen this error before but this should have been fixed. Could you please contact support via Cozy Desktop (Preferences tab) so we can get more info about it?

You should be able to start the synchronization again by removing the file from your Cozy and your computer but there's a risk of losing data and you should contact support before doing this.

I'll keep an eye on your issue.

[flo-dhalluin]

Hey, I'll send you the bug report with the app tonight. the problem is that I have no way of knowing which file is corrupted ...

[taratatach]

I see. Once we have the data from the bug report we'll run a fsck scan on your instance to find inconsistencies.

[flo-dhalluin]

Message sent. Note that I have a self-hosted instance...

[taratatach]

@flo-dhalluin I've checked with support and we've never received your message. Is your cozy's e-mail server correctly setup?

Any way, you'll have to run the fsck script yourself. You can find documentation here: https://docs.cozy.io/en/cozy-stack/cli/cozy-stack_instances_fsck/.

You can also manually send us your log files:

• zip all log* files within ~/.cozy-desktop/
• send it to [email protected]

[flo-dhalluin]

Ok, the smtp part is not documented in the self-hosting "how-to" doc. I sent a mail with logs and all but I suspect that swift@ovh has corrupted the files ...

When running fsck on the instance I get instances such as : {"type":"content_mismatch","file_doc":{"type":"file","_id":"b145f8dfbf95970408d261e109ce6c7e","_rev":"5-57db9acef637e573c8bafd771e62be27","name":"REDACTED.epub","dir_id":"b145f8dfbf95970408d261e109cacc7b","created_at":"2018-08-05T11:58:19Z","updated_at":"2019-01-16T14:31:00.897Z","tags":[],"path":"/REDACTED/REDACT/REDACTED.epub","size":"9859718","md5sum":"DEZCoQpYMzgDPg3DXUDrWA==","mime":"application/epub+zip","class":"application","is_dir":false,"is_orphan":false,"has_cycle":false},"is_file":true,"is_version":false,"content_mismatch":{"size_index":9859718,"size_file":0,"md5sum_index":"DEZCoQpYMzgDPg3DXUDrWA==","md5sum_file":"DEZCoQpYMzgDPg3DXUDrWA=="}}

my logs of the desktop app : error_cozy.log Note that I have a dozen of different corrupted file. this is details for just one of them. I redacted the file names for privacy reasons so I may have destroyed useful stuff in the process...

Since I suspect a corruption on ovh swift, I consider scraping and recreating a new instance from scratch, but I am now moderatly confident on the swift storage solution...