As others reported as well under some conditions Seafile Client never finishes downloading a library. I do have such a case while fetching a recent library using a very bad wifi connection with at most 1 MiB/s. The client downloads forever (like 2 days) without getting any further and downloading more data than the library actually contains (luckily the connections isn’t metered).
The library in this case has been shared with me. ID is
22a87787-29c0-458f-a412-bc8e2eebf318 (2017-18 - Kopie(22a87787)).
@daniel.pan you can download the log at https://download.seafile.com/lib/97ec9b9a-2740-45fe-868d-bb02a86433c0/file/seafile-log.zip (keep it private, please).
Seaf-fsck did not find anything, what I also expected because of the setup (file system with checkums in a Raid and ECC Ram)
seafile@home:~/seafile-server-latest$ time ./seaf-fsck.sh 22a87787-29c0-458f-a412-bc8e2eebf318 Starting seaf-fsck, please wait ... [12/04/18 01:59:46] fsck.c(595): Running fsck for repo 22a87787-29c0-458f-a412-bc8e2eebf318. [12/04/18 01:59:46] fsck.c(422): Checking file system integrity of repo 2017-18 - Kopie(22a87787)... [12/04/18 02:06:12] fsck.c(659): Fsck finished for repo 22a87787. seaf-fsck run done Done. real 6m26.676s user 1m49.052s sys 0m29.708s
I had an old 6.x client before and upgraded to the most recent version while having the issue, but it is still there and as you can the in the other report, copying using SeaDrive also doesn’t work because SeaDrive only works with a perfect connection.