Today some of our users told us that a lot of files stored into their shared encrypted seafile libraries have a size of 0 byte.
We tried to analyze the issue but the behavior is very strange.
In the Windows users PC (they are using different versions of seadrive to synchronize the files) in fact we have directly seen some strange behaviors:
If a user tried to upload again the right file (via seadrive or via web interface) on the one of 0 byte we saw that the file was uploaded correctly but after 5/10 seconds the size of the file return automatically to 0 byte
We closed seadrive and we tried to upload again the file via web interface, the file return automatically to 0 byte again after 5/10 seconds
We closed all the seadrive clients connected to the shared library and we started to use only web interface: we hadn’t any issue e the file maintained their correct size
We tried also to use the history to recover the file with the same behavior: with seadrive clients connected the file returned to 0 byte after some seconds, without any seadrive all worked as expected
We think that the issue is related in some way to the seadrive clients on Windows but we haven’t found any errors or strange records into the logs.
Our configuration don’t use webdav (seafdav), don’t use dockers and is a PRO version.
Do you have some ideas to solve the issue? Any way to collect some useful logs?
That’s super interesting. I was able to observe exactly the same behavior on my private Seafile server a good year or two ago (fortunately, we don’t use Seadrive in our company, or only on Mac clients).
I had numerous files that were all 0 bytes in size, fortunately none of them were important. There was nothing to be seen in the Seafile file history and the logs didn’t show anything either.
Since I only discovered it by chance, I haven’t posted it here because I couldn’t reproduce it either. And I haven’t used Seadrive for a good year now.
Sorry that I can’t help you directly, but I would like to emphasize that this is not a behavior that is unique to you.
If we remove all SeaDrive clients that have access to an encrypted shared library and we start using only Desktop Clients the problem seems disappeared.
This is not “the solution” of our issue because if only one of or our user independently install the SeaDrive client on his machine the 0 byte files appear again.
I don’t know if this tests could be useful to understand the root cause of the issue but in the next days we will remove all the SeaDrive Clients from the PC of our users and we will not available anymore to extract logs for debugging the issue…
As you mentioned you’re using mixed versions of SeaDrive. Some older versions of SeaDrive may have bugs that could lead to this issue. So first make sure all SeaDrive clients are up-to-date. If this doesn’t help, please send the log files from the client that revert files to 0 size to support at seafile.com. Thanks!