The following issue affects the Seafile client 5.1.1 and 5.1.3:
After initiating syncing an existing library (library was synced before, but had been unsynced for several months) with an existing folder, the status for this library becomes stuck at “Downloading files… 0%”. The seafdaemon process fully utilizes one thread (resulting in a constant 25% CPU usage on a system with 4 cores). Trying to cancel the process will result in displaying “Canceling” in the seafile applet, but will not actually cancel anything, when restarting the client, the status reverts to “Downloading files… 0%”. The library is roughly 30GB in size. I waited around 1 hour for the status to change, but it didn’t (so far).
The following can be found in the seafile.log (after a client restart):
[07/24/16 23:21:41] clone-mgr.c(819): Transition clone state for from [init] to [connect].
[07/24/16 23:21:41] clone-mgr.c(819): Transition clone state for from [connect] to [fetch].
[07/24/16 23:21:41] http-tx-mgr.c(4130): Download with HTTP sync protocol version 1.
[07/24/16 23:21:41] http-tx-mgr.c(1012): Transfer repo ‘’: (‘normal’, ‘init’) --> (‘normal’, ‘check’)
[07/24/16 23:21:41] http-tx-mgr.c(1012): Transfer repo ‘’: (‘normal’, ‘check’) --> (‘normal’, ‘commit’)
[07/24/16 23:21:41] http-tx-mgr.c(1012): Transfer repo ‘’: (‘normal’, ‘commit’) --> (‘normal’, ‘fs’)
[07/24/16 23:21:43] http-tx-mgr.c(1012): Transfer repo ‘’: (‘normal’, ‘fs’) --> (‘normal’, ‘data’)
Do you have any idea on how to fix this issue? Is it possible to delete the temporary data of the library (canceling the process manually) and try to start syncing it again? Any help would be appreciated!
Note: I copied this thread from the .de community forum.
Update: