MacOS Seadrive client "locks" files that were moved on a Windows Seadrive client

Seafile Client
1

Hi

I created a video to show what I try to explain with words below.

The video is about 22MB - is there a way I can provide it somehow?

I am trying Seadrive clients on Mac and Windows - the same folder is set to “Always keep downloaded” by Seadrive

I would like to explain something that I could reproduce with the MacOS 3.0.24 Seadrive client on latest seafile 13 server and also on Seafile 11 server.

Notification server is enabled.

Basically I am only moving files around.
The MacxOS SeaDrive client sometimes just “moves” it - without network traffic.

And sometimes it starts downloading the file again, which I don’t believe is the intended functionality.
You could see it in my movie file.

Is this a bug?

It never does a re-download on the windows Seadrive client and on any of the seafile clients.

Then when I move a file on the windows Seadrive client from one folder to another within the same downloaded folder and afterwords move the same file again on the MacOS Seadrive client - then the MacOS Client sort of locks the file. It doesn’t get processed on the MacOS Seadrive client anymore and is marked with a small cloud with exclamation mark

image
image284×107 9.69 KB

Only by moving the file again on the Windows Seadrive client triggers that the locking is being removed again on the MacOS Seadrive client. (Approx. Minute 1:35)

This isn’t happening on the windows seadrive or any Seafile client.

To me the locking of the file is an issue, because basically the Seadrive client on MacOS gets out of sync.

I don’t find a related log entry on the client side.

I hope it’s somehow possible and reproducible what I tried to explain.

I am happt to provide more info or to provide the video somehow

2

Hello @GITchristoph ,

You can send the video and full logs of SeaDrive to support@seafile.com.

3

Thank you - I will send the video and the logs

I will also try and explain better with the screenshots below.

I produced them independent from the video that I will email now.

I hope this helps and that more people can reproduce this.

image
image1137×1092 204 KB

image
image1140×1092 228 KB

image
image1132×1094 232 KB

image
image1131×1089 231 KB

image
image1137×1091 226 KB

image
image1128×1092 223 KB

image
image1128×1092 219 KB

4

Hi

Was someone able to reproduce this error?

5

Hello @GITchristoph ,

This issue is already being addressed internally and is expected to be fixed in the next release.

6

Thank you @feiniks !

That’s great to hear :slight_smile:

7

Hi @feiniks

I wondered if there is a time line or expected release date for the new drive client version?

I just had a look and it’s currently still on 3.0.24

Do you know if there is a way to get informed for new Seafile client releases?

Thanks a lot in advance for your answer.

8

Hello @GITchristoph ,

Since version 3.0.24 was released only recently, we may not release the next version anytime soon unless we encounter a serious bug. You may need to wait patiently for a while.

9

Hi @feiniks

I would like to mention, that I thought this is an actual bug.

I can’t say how to define seriousness here, but potentially it messes up the data structure of the servers.
We had to stop using the Seadrive client on macOS because it’s not reliable when moving files around.

I don’t want to argue this topic with you and will wait patiently.
But I also wanted to explain my point of view and actually hope you reconsider.

10

Hello @GITchristoph ,

Thank you for your feedback. We will do our best to release the next version as soon as possible.

1 Like