Open
Description
starting from here: https://help.nextcloud.com/t/desktop-client-3-4-0-destroys-local-time-stamp-and-keeps-uploading-data-to-server/128512/54?u=wwe
I didn’t find time to build reliable recovery procedure from this information as I’m not an expert in mysql but it should work as following:
- find files with invalid mtime
- find the most recent version (if many) of the file which has valid mtime
- perform one of the possible recovery options:
- safe: touch the file with valid mtime (and remove version in 2nd step)
- storage efficient: move version file to the original location and overwrite bad file
- perform occ files:scan all
additional sugar:
- compare the version file you use for recovery with the file in the system (diff/checksum) - AFAIK the contents are unchanged, so file contents and versions should be same
- remove newer versions having invalid mtime (there are github reports when upload with invalid mtime happened multiple times)
I didn’t investigate further - NC devs might know from the top of the head - i think oc_filecache table is not separated by user so if collect the information from DB you don’t need to iterate over each user to identify and recover the files, it should work in one go…
Metadata
Metadata
Assignees
Labels
No labels