I get some users which get problems with the files and folders sync: there are big differences between their computers and the Seafile server.
See an example of these differences for the same folder (on from the Seadrive client and the other one from the seafile server):
Hi，
can you show a more complete screenshot of the files under this folder? It could be that the directory is no longer synced with the server, can you test if you can upload files properly under this folder ? And whether uploading a file under this folder on the server can be synchronized locally?
I “fixed” it by Resyncing. Unfortunately there is a new local folder created then for the SeaDrive.
It could be a problem, if I’m not aware that there is something wrong. Don’t know if it has implications at other places in the file tree as well when getting the -2005 Error.
The cause for the original issue was that there were two “seadrive file provider” extension processes running on the computer. This could cause sync problems.
@madein Your issue may be different. But if you upgrade to 3.0.9, there may be more information about the error in the “file sync error” dialog when you see a file is in error state. You can check that.
3.0.9 also solve the potential issue of two extensions running.
@Jonathan No, it’s not related to two seadrive instances. I have only one instance running, 3.0.9, and get the same error.
In logs: [05/13/24 12:26:18] FileProviderExtension.m(256): Failed to get dirent for 9a516534-3ab2-4e1d-82fd-db7d35c4cd5a:NewFolder/[skipped]/DSF4208.RAF
Maybe yes, maybe not. Actually, it is not important at all. The problem is I tested the latest versions of SeaDrive client and SeaFile server for a few hours and faced this bug. This is basic functionality and should not raise any questions. Instead, I got duplicates of some files. And in the end the system cannot download the folder at all. There are big, big questions for your testing department. As for me personally, it is with great regret that I had to abandon the prospects of using such a convenient tool.
It’s pity that you quit using SeaDrive/Seafile at all. I personally use SeaDrive everyday with a lot of files. I didn’t have similar issues. I believe this issue may be related to some special situation. If you can provide more information we can find out the cause.
