Library desynced upon reboot

Seafile Client
1

After a client computer crash (unsure if related or just a red herring), one of the four synced libraries no longer appear to be synced. [$ seaf-cli status] only lists three libraries instead of the previous 4. Looking at the “Last Update” column in seahub I can also see the very last change to the unsynced lib was just prior to the system crash.

What should be done? Is this expected?

Would be good if seaf-cli could track these corrupted/lost libraries and be reported by the ‘status’ command. Otherwise users could go months without even realizing some libraries have become untracked, potentially resulting in a loss of data down the line.

Running on debian testing

seafile-daemon,seafile-cli,python3-seafile,libseafile0t64  9.0.7-1

server version 11.0.12

2

Hi @layr , this may be the result of a computer crash that prevents the client from getting the synced library locally, in such case, the library is automatically desynchronized. So seaf-cli can’t not see the libraries that had been synchronized before. You can check the seafile.log to see if there is a keyword like Auto deleted repo.

3

Cannot find any occurrences of ‘deleted repo’ in server-side logs.

To re-iterate, crash was on client-side. Server has been running OK.