Can't execute executable from SeaDrive

xenorexian · July 7, 2017, 9:26am

Hi.
Is this a known issue?
I just says, that it can’t start the program, because the provided path doesn’t exist.
Could it be something with SeaDriveFS and NTFS permissions?

Jonathan · July 9, 2017, 12:04pm

Currently SeaDrive only allows the current user to access the files. So if an executable requires admin permission to execute, it has to be run as administrator. So the administrator user cannot find the path. This is a limitation we plan to remove in later release, before 1.0.

cr18 · June 3, 2018, 10:58pm

Hi, any news on this issue? I’d like to use Seadrive to sync my developper folder, obviously not allowing executable to run is problematic in this use case…

Thanks

bionade24 · June 4, 2018, 7:29pm

SeaDrive is Beta. The only way is to create a simple bash script who indexes the files and make them executable. This shouldn’t be a problem.

cr18 · June 4, 2018, 8:06pm

The problem is not that simple. Chmod +x doesn’t affect files in latest Seadrive beta on the Mac (0.9.1). Can we have an official word on this?

maweber · October 3, 2018, 12:15am

same with 0.9.5

cr18 · December 14, 2018, 9:05pm

Any news on this? Is it a FUSE limitation?

Di_Tsi · September 1, 2019, 7:05pm

Because of this I have to use both Seafile and Seadrive. Seafile for dev and script directories. When it can be fixed?

antares · January 16, 2024, 6:37pm

I have this issue right now on SeaDrive for macOS. No binary is executable. Even when I compile it again and put it on SeaDrive, the permissions are lost. On top, not even chmod can change that. Any idea what is going on?

antares · January 16, 2024, 8:39pm

Quick update on this: When I move the executable off the drive to some other folder on my Mac, I can modify permissions and the executable works again…but as soon as SeaDrive touches the binary, it stops being executable.

Johnny · January 17, 2024, 6:55pm

Same here. Can’t use Seafile Drive Client for my development work because I’m unable to run executables.
@Jonathan is this limitation already removed, but requires configuration or does this still exist? If so, are there any plans to resolve the issue?

Jonathan · February 8, 2024, 10:49am

This will be fixed in the next version (3.0.8).

atusay · December 31, 2024, 2:00am

Any chance executing files will be available for linux in seadrive client? or should I just use the seafile client?

Jonathan · January 4, 2025, 6:38am

The linux seadrive should allow executing files. What issues do you have?

robm · January 2, 2026, 6:30pm

@Jonathan
I’m unable to execute any files from within the seadrive mount, nor am I able to chmod +x – it seems to be a noop.

[rob@pc foo]$ stat example.sh
File: example.sh
Size: 25        	Blocks: 0          IO Block: 4096   regular file
Device: 0,145	Inode: 113         Links: 1
Access: (0644/-rw-r–r–)  Uid: ( 1000/     rob)   Gid: ( 1000/     rob)
Access: 1970-01-01 01:00:00.000000000 +0100
Modify: 2026-01-02 18:26:58.000000000 +0000
Change: 1970-01-01 01:00:00.000000000 +0100
Birth: -


[rob@pc foo]$ chmod +x example.sh


[rob@pc foo]$ stat example.sh
File: example.sh
Size: 25 Blocks: 0 IO Block: 4096 regular file
Device: 0,145 Inode: 113 Links: 1
Access: (0644/-rw-r–r–) Uid: ( 1000/ rob) Gid: ( 1000/ rob)
Access: 1970-01-01 01:00:00.000000000 +0100
Modify: 2026-01-02 18:26:58.000000000 +0000
Change: 1970-01-01 01:00:00.000000000 +0100
Birth: -

As you can see, it’s impossible to set the file mode to be executable – chmod does nothing. This is super annoying when storing scripts in SeaDrive as you might imagine!

The drive appears to be mounted normally (i.e. without noexec)

$ mount
seadrive on /home/rob/SeaDrive type fuse.seadrive (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

Any ideas?

Jonathan · January 4, 2026, 4:16am

If you upload an executable file with sync client, and then access it via SeaDrive, does it appear as executable? Can you execute it?

robm · January 4, 2026, 4:30pm

Thanks for checking in @Jonathan!

If I upload an executable file with the sync client, then access via SeaDrive, it is not executable from the SeaDrive mount.

So execution works fine via SeaFile, but is broken in SeaDrive.

Save an executable file via SeaFile:

$ printf '#!/bin/bash\necho "hello world"\n' > ~/SeaFile/example.sh
$ chmod +x ~/SeaFile/example.sh

Stat from SeaFile: Is executable

$ stat ~/SeaFile/example.sh
  File: example.sh
  Size: 31        	Blocks: 8          IO Block: 4096   regular file
Device: 0,28	Inode: 6394568     Links: 1
Access: (0755/-rwxr-xr-x)  Uid: ( 1000/     rob)   Gid: ( 1000/     rob)
Access: 2026-01-04 16:18:16.070248217 +0000
Modify: 2026-01-04 16:18:14.747248157 +0000
Change: 2026-01-04 16:18:19.340248364 +0000
 Birth: 2026-01-04 16:18:14.747248157 +0000

$ ~/SeaFile/example.sh
hello world

Stat from SeaDrive: Is not executable

$ stat ~/SeaDrive/example.sh 
  File: example.sh
  Size: 31        	Blocks: 0          IO Block: 4096   regular file
Device: 0,79	Inode: 382         Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/     rob)   Gid: ( 1000/     rob)
Access: 1970-01-01 01:00:00.000000000 +0100
Modify: 2026-01-04 16:18:14.000000000 +0000
Change: 1970-01-01 01:00:00.000000000 +0100
 Birth: -

$ ~/SeaDrive/example.sh
bash: /home/rob/SeaDrive/example.sh: Permission denied

(chmod +x from SeaDrive has no effect, permissions remain 0644/-rw-r–r–)