Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Drive File Stream conflicts with FUSE for macOS #503

Open
danielbair opened this issue May 14, 2018 · 7 comments

Comments

@danielbair
Copy link

commented May 14, 2018

I have found that com.github.osxfuse.filesystems.osxfuse and com.google.dfsfuse.filesystems.dfsfuse conflict.

To get FUSE for macOS to work I have to run:
sudo kextunload -b com.google.dfsfuse.filesystems.dfsfuse
If I don't do this then I get this error:
mount_osxfuse: the file system is not available (255)

I am reporting this in case any others might encounter this issue.

@dictvm

This comment has been minimized.

Copy link

commented Jun 4, 2018

This is indeed quite a problem since we switched from Google Drive to File Stream. Sometimes it works after dancing around a fire while installing, uninstalling and rebooting a bit.

@armarti

This comment has been minimized.

Copy link

commented Sep 10, 2018

Same issue here when trying to install Google Drive File Stream. To get it to work I needed to unload osxfuse with sudo kextunload -b com.box.filesystems.osxfuse (not sure sudo is necessary, but that's what I did). I'm sure something else is broken somewhere but I don't know what yet.

@taiyodayo

This comment has been minimized.

Copy link

commented Jan 16, 2019

I have the same problem and it is quite a big problem for me since our office switched entirely to Google drive file stream.
Has anyone found a workaround yet?

@beaulac

This comment has been minimized.

Copy link

commented Jun 26, 2019

Issue still occurs with osxfuse 3.9.2

Incompatibility works both ways – Google Drive File Stream is not able to start if the osxfuse kext is loaded:

... stderr: (kernel) Kext com.google.drivefs.filesystems.dfsfuse start failed (result 0x5).
... stderr: (kernel) Kext com.google.drivefs.filesystems.dfsfuse failed to load (0xdc008017).
... stderr: (kernel) Failed to load kext com.google.drivefs.filesystems.dfsfuse (error 0xdc008017).
... stderr: Failed to load /Library/StagedExtensions/Applications/Google Drive File Stream.app/Contents/MacOS/dfsfuse.kext - (libkern/kext) kext (kmod) start/stop routine failed.
... stderr: Unhandled kextutil status: 6
... stderr: mount_dfsfuse: the file system is not available (113)
... mount.cc:108:Mount Mount status flags: 0x5c4
... stderr: fuse: failed to mount file system: Unknown error: 113

Workaround:
sudo kextunload -b com.github.osxfuse.filesystems.osxfuse to use file stream

@bfleischer

This comment has been minimized.

Copy link
Member

commented Jun 26, 2019

This is what happens if a developer tries to rebrand osxfuse to put their own name on it (dfsfuse) and does a poor job. Say thanks to Google. There is nothing I can do from this end.

@csjx

This comment has been minimized.

Copy link

commented Sep 18, 2019

I use keybase.io and it too has a FUSE implementation (kbfs). It seems to not load at times, and I at some point found a post that com.intel.kext.intelhaxm conflicts with it. I had the same Google Drive File Stream issue with the dfsfuse kext not loading, so I tried sudo kextunload -b com.intel.kext.intelhaxm. It worked - the Sign In screen appears now after hours of troubleshooting. I probably need the intelhaxm extension with Android Studio or the like, so I may have to manually load and unload the extensions. 😐

@bfleischer

This comment has been minimized.

Copy link
Member

commented Sep 18, 2019

@csjx The issue you are seeing is most likely caused by macOS running out of free device slots. The number of device slots is limited. Intel HAXM and kbfs each need a free device slot. A lot of other software does, too. VirtualBox for example needs multiple device slots. Some virus scanners take up device slots, too. This can result in macOS running out of device slots and this prevents kbfs from loading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.