"Failed to get commit" in seafile.log

What is the meaning of “virtual-repo.c(969): Failed to get commit …” in seafile.log? Seaf-fsck and seaf-gc say all okay.
I think, it comes from a Seafile Client and it fills up the file every 2 minutes.

I’ve completely reinstall the client on the Laptop, but the same.

@daniel.pan
Does nobody have an idea?

@Jonathan

Can you post the detailed message, including the commit id? Then I can tell you how to check whether the commit object exists.

[12/18/17 14:00:03] virtual-repo.c(969): Failed to get commit 87f71be3-0527-4676-b9b4-427c1934c821:98563634.

Thanks @Jonathan

The path is seafile-data/storage/commits/87f71be3-0527-4676-b9b4-427c1934c821/98/563634xxxxx. ‘x’ represents some characters. Do you find this file?

This file 563634xxxxx is missing.

Have you ever synced a sub-folder of the library ‘87f71be3-0527-4676-b9b4-427c1934c821’? If so, you can try to stop syncing that folder. It some how relies on that missing commit object.

Hi Jonathan,

My solution was to export the whole library (perfect), then delete and recreate a new one and import the data back. Now the sync works.

Just to mention that I encountered the same error:

==> seafile.log <==
[09/12/2018 04:34:59 PM] http-server.c(1000): Failed to get commit b14c59bd06051701cc1465dd7bd67ac2e1956fa6 for repo 24210125-f6a7-4939-a11c-f57dba3f0797.
[09/12/2018 04:35:31 PM] http-server.c(1000): Failed to get commit b14c59bd06051701cc1465dd7bd67ac2e1956fa6 for repo 24210125-f6a7-4939-a11c-f57dba3f0797.
[09/12/2018 04:35:50 PM] http-server.c(1000): Failed to get commit b14c59bd06051701cc1465dd7bd67ac2e1956fa6 for repo 24210125-f6a7-4939-a11c-f57dba3f0797.

With Seafile 6.2.5 on Debian