mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1632] Apple Silicon (M1): Installing via brew fails due to missing FUSE #856
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#856
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JulianAssmann on GitHub (Apr 24, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1632
I tried installing
s3fsviabrewon a Macbook Air (late 2020), which has the new Apple Silicon M1 chip inside, by typing:brew install osxfuse(Restarting)
brew install s3fsbut it failed with the message
Error: s3fs has been disabled because it requires FUSE!I also tried compiling
s3fsby myself by typingbut it fails on the
configurestep with the error:OS
MacOS Big Sur
Kernel information (
sysctl kern.version)kern.version: Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST 2021; root:xnu-7195.81.3~1/RELEASE_ARM64_T8101
@gaul commented on GitHub (Apr 25, 2021):
I believe that the Homebrew error is intentional from their maintainers. The Homebrew MacFUSE 3.x version is older and does not support newer macOS versions and the newer MacFUSE 4.x versions have a different license that Homebrew objects to. I believe that you can install MacFUSE 4.x yourself and osxfuse/osxfuse#754 suggests that M1-based MacBooks require this. Unfortunately I don't have a recent MacBook to test this so we would appreciate your testing and feedback. If you can get this working we should rewrite the installation instructions for other users.
@ryan-williams commented on GitHub (Apr 25, 2021):
I'm not sure the issue with
brew/osxfuseis specific to M1 hardware. I had to work around it on a 2017 (pre-M1) macbook pro recently.I think I just uninstalled the
osxfusecask:and installed macFUSE (clicking through various scary-sounding modals).
My
s3fsis just installed viabrew. It's interesting thatbrew infoimpliess3fsis disabled due to FUSE support no longer being available via brew:I also have an M1 macbook I can try this on at some point / if you think it would be specifically useful.
@ryan-williams commented on GitHub (May 5, 2021):
Just trying this on my M1 macbook, and sure enough,
brew install s3fsjust fails w the error msg reported above:What's a little strange is that I installed macFUSE (including booting into recovery mode and enabling system extensions), similarly to what I did on my older macbook.
I'm wondering if on my older macbook, s3fs registered that I had the
osxfusecask installed at one point, and so it proceeded to install. afaict, I have FUSE, so s3fs should be able to run.Unless the issue is truly that s3fs devs intentionally don't want s3fs to be runnable against newer macFUSE due to licensing concerns…(I misremembered; the licensing issues are between Homebrew and FUSE: https://github.com/Homebrew/homebrew-core/pull/64491)I'll poke at a whether there are other ways to install s3fs on my M1, and report back; I really need it, and am switching to this M1 full-time soon as I have to return the older macbook 🙀
@ryan-williams commented on GitHub (May 5, 2021):
brew install --cask osxfuseworkedbrew info osxfuselooks OKbrew install s3fsstill erroring@ryan-williams commented on GitHub (May 5, 2021):
Trying to build
s3fsfrom source:Download+Untar:
./autogen.sh(required
brew install automakeforaclocalexecutable)Naively running
./configure --prefix=/usrran me intoNo package 'libcrypto' founderror; based on suggestions inbrew info openssl, I provided necessary lib/include paths via:Then
./configure --prefix=/usrworkedNow
makeis failing:ld: symbol(s) not found for architecture arm64:Any guidance appreciated 🙏
@gaul commented on GitHub (May 8, 2021):
Related: GoogleCloudPlatform/gcsfuse#514
@caslan34 commented on GitHub (Jun 12, 2021):
hello, did you find solutions ?
@gaul commented on GitHub (Jun 28, 2021):
Could you try this external Homebrew cask:
https://github.com/gromgit/homebrew-fuse/
If it works can you update README.md?
@harijay commented on GitHub (Jul 14, 2021):
Hi All I got this working as documented in the Compilation.md
First I had to make sure I had turned off "Open using Rosetta" for my shell which was the iterm2 app. Then the steps I followed were
In previous attempts I had turned on Rosetta for iterm and it responded with "ld: symbol(s) not found for architecture x86_64"
I then did a make clean and followed the steps above and was able to mount s3 bucket without any problems
@gaul commented on GitHub (Jan 4, 2022):
Does #1817 resolve this issue?
@gmuth commented on GitHub (Jan 17, 2022):
Steps 1 to 4 work for me (M1, 12.1).
configure.sh fails:
having openssl 3 installed I solved this issue with:
export PKG_CONFIG_PATH="$HOMEBREW_PREFIX/opt/openssl@3/lib/pkgconfig"./make then produced the arm64 executable in directory src.
@jauharvp commented on GitHub (Apr 15, 2022):
#./autogen.sh#./configure#export PKG_CONFIG_PATH="/opt/homebrew/opt/openssl@1.1/lib/pkgconfig/"#./configure#make#sudo make installThis is worked for me, but Whenever I try to access the mounted bucket, either finder or terminal freeze.
Anyone else having the same problem, or just me?
@gmuth @harijay
@jauharvp commented on GitHub (Apr 24, 2022):
I tried numerous times, the system getting hung when I mount the bucket with s3fs.
@ryan-williams commented on GitHub (May 3, 2022):
Revisiting this again about a year after my last attempt…
So far so good,
which s3fsandman s3fsseem to work.The first time I tried to actually invoke

s3fs, I was required to enable system extensions, by booting into recovery mode and changing the kernel security policy:then I was able to go into System Preferences and enable the macFUSE kernel extension.
Finally, I ran
s3fs:Seemingly succeeds. However, all of these commands hang, and are impervious to
^C/^D/kill -9:Even rebooting my computer doesn't really work, at this point: various apps refuse to quit, and after I force quit them, the OS just shows an empty desktop, with the top menu bar gone. I had to use the power button to turn off the computer completely.
I tried again with
-f, it just prints the initial command and then hangs the same:I gave up at this point.
@gmuth commented on GitHub (May 3, 2022):
We have two issues here. One issue was to produce a M1 executable. That seems to be the solved.
Another issue is that the executable doesn't work as expected. So someone knowledgeable needs to look into this issue and investigate what's wrong with the binary produced.
When switching CPUs sometimes the byte order causes issues: little or big endian. But that's just guessing.
@gaul commented on GitHub (May 4, 2022):
s3fs runs on Raspberry Pis so I believe it should work fine from that perspective. If it is hanging, you should try debug logging
-dand attaching a gdb backtrace.@xy-xin commented on GitHub (Aug 29, 2022):
@ryan-williams > My situation was the same with you. Now i've switched to s3cmd.
@xy-xin commented on GitHub (Aug 29, 2022):
@harijay It works! So the solution is not using the brew's s3fs-mac.
@jlee9595 commented on GitHub (Feb 23, 2023):
@ryan-williams also experiencing these same exact issues in 2023 :(
@alfiedotwtf commented on GitHub (Mar 15, 2023):
@ryan-williams @jlee9595 Can confirm here on an M2.
s3fswill happily mount, but then not only willlshang, the whole filesystem slows to a crawl. Even opening System Preferences hangs and "Force Quit" starts showing everything in red.Has anyone found a work around yet?
@alfiedotwtf commented on GitHub (Mar 19, 2023):
I stand corrected! I reinstalled
gromgit/fuse/s3fs-macand it worked 😍Edit: interesting... it only seems to work when running with
-o dbglevel=info -f -o curldbg. If I remove that, I get the freezing issue right away.@alfiedotwtf commented on GitHub (Mar 19, 2023):
Ok, I think I found something interesting - the m2 hanging problem seems to be fixed when you use
-f, which keeps it in the foreground. People on m2: give it a go and see if it works!@ggtakec commented on GitHub (Mar 26, 2023):
@alfiedotwtf
If you're deadlocking(or something similar) only when you don't use
-f, then I'm concerned about the relationship between pthreads and forks.In s3fs, I believe that the thread do not have been started before it was forked, but it sounds like that deadlock situation with it.
This is just something I'm curious about, and I have no confirmation of anything.
@elliotkendall commented on GitHub (Apr 19, 2024):
I'm still getting the "This formula requires macFUSE. Please run
brew install --cask macfusefirst." error when macfuse is already installed. This is on macOS 14.4.1