Error in client when syncing files over 200mb

Hi, I have Seafile on a Raspberry 4b. My client is 7.0.7. When I put files over 200mb in my folder for syncing I get an error showing an exclamation mark in the icon and also in the log file but then it all syncs fine. Can I do something against this behavior? Thank you!

Hi Tillski,

welcome to the Seafile Community Forum!

Can you please post the error message from the log file? How do you check that the sync was successul? Does the exclamation status icon disappear after a while?

Ralf

Here is what it says. I reinstalled the client on my desktop pc, didn’t help. Fun thing is on my new laptop this error does not occur. Actually the exclamation status icon disappears after looking at the error only. I see the files are all in sync (green check) on server and laptop and are fully functioning.

[05/03/20 23:15:47] sync-mgr.c(582): Repo ‘ARCHIVE’ sync state transition from ‘synchronized’ to ‘committing’.
[05/03/20 23:15:47] cdc.c(237): CDC: failed to open F:/ARCHIVE/Free 3D Sketchup Scene Scandinavian Studio by Cuong Le13.10L.zip.
[05/03/20 23:15:47] …/common/fs-mgr.c(870): Failed to chunk file with CDC.
[05/03/20 23:15:47] repo-mgr.c(1206): Failed to index file F:/ARCHIVE/Free 3D Sketchup Scene Scandinavian Studio by Cuong Le13.10L.zip.
[05/03/20 23:15:47] repo-mgr.c(3822): All events are processed for repo 385d5866-5324-4731-afc1-4104b86608e9.
[05/03/20 23:15:47] sync-mgr.c(574): Repo ‘ARCHIVE’ sync is finished but with error: Error when indexing
[05/03/20 23:15:47] sync-mgr.c(582): Repo ‘ARCHIVE’ sync state transition from ‘committing’ to ‘error’.
[05/03/20 23:15:55] sync-mgr.c(582): Repo ‘ARCHIVE’ sync state transition from ‘synchronized’ to ‘committing’.
[05/03/20 23:15:58] repo-mgr.c(2577): Creating partial commit after adding Free 3D Sketchup Scene Scandinavian Studio by Cuong Le13.10L.zip.
[05/03/20 23:15:58] sync-mgr.c(582): Repo ‘ARCHIVE’ sync state transition from ‘committing’ to ‘uploading’.
[05/03/20 23:15:58] http-tx-mgr.c(1157): Transfer repo ‘385d5866’: (‘normal’, ‘init’) --> (‘normal’, ‘check’)
[05/03/20 23:15:58] http-tx-mgr.c(1157): Transfer repo ‘385d5866’: (‘normal’, ‘check’) --> (‘normal’, ‘commit’)
[05/03/20 23:15:58] http-tx-mgr.c(1157): Transfer repo ‘385d5866’: (‘normal’, ‘commit’) --> (‘normal’, ‘fs’)
[05/03/20 23:15:58] http-tx-mgr.c(1157): Transfer repo ‘385d5866’: (‘normal’, ‘fs’) --> (‘normal’, ‘data’)
[05/03/20 23:15:58] http-tx-mgr.c(1157): Transfer repo ‘385d5866’: (‘normal’, ‘data’) --> (‘normal’, ‘update-branch’)
[05/03/20 23:15:58] http-tx-mgr.c(1157): Transfer repo ‘385d5866’: (‘normal’, ‘update-branch’) --> (‘finished’, ‘finished’)
[05/03/20 23:15:58] sync-mgr.c(582): Repo ‘ARCHIVE’ sync state transition from ‘uploading’ to ‘initializing’.
[05/03/20 23:15:58] sync-mgr.c(881): Removing blocks for repo ARCHIVE(385d5866).
[05/03/20 23:15:58] sync-mgr.c(582): Repo ‘ARCHIVE’ sync state transition from ‘synchronized’ to ‘committing’.
[05/03/20 23:15:58] repo-mgr.c(3678): All events are processed for repo 385d5866-5324-4731-afc1-4104b86608e9.
[05/03/20 23:15:58] sync-mgr.c(582): Repo ‘ARCHIVE’ sync state transition from ‘committing’ to ‘synchronized’.

Is there space left on the disk where the Seafile folder resides? (The one chosen on setup)

Yes. A lot.

What file system do you use?

I’m using mysql.

That’s your database. I am more interested in your local hard drive’s file system. NTFS and ext are ok. But I once encountered very weird behavior on a extFAT formated hard drive. So please check your hard drive file system.

It is NTFS. :frowning:

Sooo, when I change the time of the sync interval high enough then there are no more errors. The bigger the file the more seconds I need. A 5GB file needs around 100 seconds interval. When I drag and drop a file in a sync folder on my SSD then Windows seems to be do something in the background which interferes with the seafile sync. Maybe it is also another program than Windows? How can I find out? Would like to set back the interval a bit lower. I guess it is some file scanner…