SeaDrive not syncing a library

Seafile Client
1

Hi,

SeaDrive client 0.5.1 (was the same with previous versions) does not “sync” some of the libraries from the Seafile 6.0.8. The seadrive log file contains the following errors regarding one of the libraries that fail to sync:

[02/26/17 17:20:33] utils.c(1719): Failed to inflate. [02/26/17 17:20:33] fs-mgr.c(999): Failed to decompress dir object f7cd6969a17958e742e8c3217f8679b3a985526a. [02/26/17 17:20:33] repo-tree.c(177): Failed to get dir f7cd6969a17958e742e8c3217f8679b3a985526a from repo c8c0cb37-554d-422e-a617-98c72642b37e. [02/26/17 17:20:33] repo-tree.c(194): Failed to get dir f7cd6969a17958e742e8c3217f8679b3a985526a from repo c8c0cb37-554d-422e-a617-98c72642b37e. [02/26/17 17:20:33] repo-tree.c(194): Failed to get dir 767879f0e79abbb12ce5da07178641021259b3ca from repo c8c0cb37-554d-422e-a617-98c72642b37e. [02/26/17 17:20:33] repo-mgr.c(1000): Failed to load tree for repo c8c0cb37-554d-422e-a617-98c72642b37e.

I assumed this to be a problem with a repo, however running seaf-fsck on this specific repo/library does not find any errors:

Starting seaf-fsck, please wait ... [02/26/17 16:59:12] fsck.c(586): Running fsck for repo c8c0cb37-554d-422e-a617-98c72642b37e. [02/26/17 16:59:12] fsck.c(413): Checking file system integrity of repo 3d print(c8c0cb37)... [02/26/17 17:02:30] fsck.c(650): Fsck finished for repo c8c0cb37. seaf-fsck run done

Any ideas?

2

Some metadata objects are corrupted on your local computer (due to hard shutdown etc.). You can re-login the account to solve the problem.

BTW, we’re improving error notification in the next version so that such kind of errors will be more obvious.

3

Ah, thanks! That indeed solved the problem.