Seafile Drive client for Mac is ready for testing!

You can download is in Seafile download page.

In this version, you have to install a third party program OSXFuse separately. In later version, we will bundle it together with Seafile Drive client.

This version is considered to be stable for file accessing and editing. But integrating with Mac operating system still need to be improved. The know limitation currently is that files in Drive client can’t be searched.

Best regards,
Daniel Pan


Many thanks for this! So far, with this exception, it seems to work fine.

Bug: The SeaDrive created filesystem does not support executable scripts. Existing shell scripts with +x lose it, and I’m unable to chmod +x it back (file attributes aren’t modified).

Big Thanks!

There is another bug…
infinity loop of:

[10/19/17 09:40:12] file-cache-mgr.c(2091): Failed to get seafile-mtime attr from /Volumes/Home/Users/alex/.seadrive/data/file-cache/e6d20ad7-978b-4efc-8bcb-110aa2cfe64a/Documents/Virtual Machines.localized/Windows 10

[10/19/17 09:40:17] file-cache-mgr.c(2091): Failed to get seafile-mtime attr from /Volumes/Home/Users/alex/.seadrive/data/file-cache/e6d20ad7-978b-4efc-8bcb-110aa2cfe64a/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-s001.vmdk.

[10/19/17 09:40:22] file-cache-mgr.c(2091): Failed to get seafile-mtime attr from /Volumes/Home/Users/alex/.seadrive/data/file-cache/e6d20ad7-978b-4efc-8bcb-110aa2cfe64a/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Virtual Disk-s001.vmdk.

Restarting the driveclient doesn’t help.

after a while the client continues to transmit the other files… :slight_smile:

Another bug is, that the file creation date is always “Thursday, 1. January 1970 at 01:00”
It doesn’t matter if the file was copied/moved from another location to seafile drive or is copied directly on the seafile drive volume.

When has the library been created?

The Files have been created at 15-16.10.2017 but 01.01.1970 is always set, no matter what the real creation date has been…

using “stat” from the console the date attributes are looking like this:
~/SeaDrive/My Library/My Photos/Camera|alex$ stat DSC03996.JPG
838860803 45 -rw-r–r-- 1 alex staff 0 4554752 “Jan 1 01:00:00 1970” “Oct 26 20:43:20 2017” “Jan 1 01:00:00 1970” “Jan 1 01:00:00 1970” 65536 8896 0 DSC03996.JPG

Other File Formats:
~/SeaDrive/My Library|alex$ stat Wärmepumpe1.xlsx
838860803 115 -rw-r–r-- 1 alex staff 0 27208 “Jan 1 01:00:00 1970” “Dec 3 09:28:24 2016” “Jan 1 01:00:00 1970” “Jan 1 01:00:00 1970” 65536 56 0 Wärmepumpe1.xlsx

As you can see only the “modified date time” ist correct. The file creation time “birth time” ist wrong.

While googling I found this on stack exchange:
"The POSIX standard only defines three distinct timestamps to be stored for each file: the time of last data access, the time of last data modification, and the time the file status last changed.

That said, modern Linux filesystems, such as ext4, Btrfs and JFS, do store the file creation time (aka birth time), but use different names for the field in question (crtime in ext4, otime in Btrfs and JFS). However, currently Linux does not provide a kernel API for accessing the file creation times, even on filesystems supporting them."

So perhaps we cannot get fixed this inconvenience and have to live with it…

And when has the library been created?

“My Library” was created in spring of this year.

By pure coincidence I’m just sitting here in front of a Win10 PC and can’t see the directory and file creation dates… :slight_smile: (field is left empty … on Mac it was 01.01.1970)

So might be not a MAC problem…

  • client version on Windows is 0.7.0
  • Server version is 6.0.5 running on Debian 8 with Btrfs

This is a typical Problem of Unix. At this date Unix was born. And when the program don’t know the time, they always set the time to the 1.1.1970.

Are you aware that SeaDrive 0.8.5 Mac still has the same bug as Seafile Client had (forcing the MacBook Pro to switch to AMD graphics card)?
Please raise this fix in the the todo-list for SeaDrive on Mac.
Thanks !
Edit: The temporary manual fix used initially with Seafile Client (Seafile Client 6.1.0 requires discrete/dedicated GPU on macOS) works fine though. But it’d be better to change that for next beta build, so it does not reset on people on next update. :slight_smile:

See Seafile drive client 0.8.5 is ready! Bug fixes and improved MacOS support .Thanks for reporting anyway.