Seafile Linux Client not syncing / downloading

Seafile Client
22

I re-checked the error. It means the client reaches the maximum number of files to monitor the changes. This should not affect file syncing.

23

You should check your maximum allowed number of open files.

And most likely also increase the inotify limit: linux - Kernel inotify watch limit reached - Unix & Linux Stack Exchange

1 Like
24

Hi @shoeper @daniel.pan,

Thank you for your help, the sync process for 800 Go finally ended with sucess (12h of syncing between two debian VM on the same host).

setting on the server cc-net.conf

SERVICE_URL = https://*

fixed the syncing startup

pysearpc.common.SearpcError: Argument can't be NULL

Seting inotify limit to
sudo sysctl fs.inotify.max_user_watches=524288

fixed this error message

[05/29/18 10:05:48] wt-monitor-linux.c(539): [wt mon] fail to add watch to /nfs/bacula/biblissima/files/Pool/#recycle/Exports_BAM/exports_20160926/departement_manuscrits/arabe_cote/DĆ©partement des manuscrits/Arabe/@eaDir/FRBNFEAD000089880.xml: No space left on device.

renaming file names (5 files) fixed

[05/29/18 10:05:51] repo-mgr.c(1161): File name Ō…Ū¶_Ō…Ū¶_3.ZIP contains non-UTF8 characters, skip.

I had no problem with disk space on the client

To let you know, the CPU process was very high on the client, but it ended sucessfully with no crash.

best regards,

Gautier

25

Just curious: Isnā€™t rsync much better for such a scenario?

26

Technically, sure.
But, the use case was :

  • Users previoulsuy accessed files (Archive) on a Synology NAS connected to the intenet (WebDav)
  • The NAS crashed
  • We had a backup on a NFS mount not accessible on the internet (no webDav)
  • Users also used Seafile for current work
  • It was then natural to restore the archive into Seafile
  • now users can sort the archive and current work

Regards

1 Like
27

Glad to know it works.

1 Like