mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1804] s3fs mounts hang and slow OS with macOS 12 (Monterey) #921
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#921
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 @pngafney on GitHub (Nov 5, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1804
Additional Information
The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD
Version of s3fs being used (s3fs --version)
example: 1.00
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
V1.87
Kernel information (uname -r)
21.1.0
GNU/Linux Distribution, if applicable (cat /etc/os-release)
macOS Monterey 12.0.1
s3fs command line used, if applicable
/etc/fstab entry, if applicable
N/A
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages
Details about issue
s3fs mount command runs but when trying to access the mount it hangs from both command line and from a Finder window. Once this happens the OS runs slow and will not reboot without a hard power off and on. This happens when I've upgraded from a working macOS 11 OS and a clean install of macOS 12. Using MacFUSE 4.2.1
@niebaopeng commented on GitHub (Nov 21, 2021):
Me too
Stuck on ls or cd or df or other command
12.0.1 osx
macfuse 4.2.3
s3fs 1.8.7
@georgedanker commented on GitHub (Nov 28, 2021):
Exactly the same issue here.
@NicTorgersen commented on GitHub (Dec 9, 2021):
On Monterey, it seems the only way I could get this to work is without running
s3fsas a daemon. E.g. by passing the -f parameter.s3fs <bucket> <mountpoint> -f -o passwd_file=$HOME/.passwd-s3fs.@NoraGithub commented on GitHub (Mar 2, 2022):
same here
@NoraGithub commented on GitHub (Mar 2, 2022):
@ggtakec would you mind having a look at this issue
@ggtakec commented on GitHub (Mar 5, 2022):
I found the following line in the log I received.
It is unlikely that you have specified an invalid option in the options when starting s3fs, so it is possible that an error occurred during the initialization of s3fs.
Is it possible to add
_netdev?(please try it if you can.)
It may have been mounted before the Network was up.
@NoraGithub commented on GitHub (Apr 6, 2022):
I cannot try it, i am not that familiar with this project but a user who want to use it as expected. MOREOVER, i am only a python coder and i don't konw how to add
_netdevto anywhere@NoraGithub commented on GitHub (Apr 6, 2022):
would you mind trying the way as above @NicTorgersen
@NoraGithub commented on GitHub (Apr 6, 2022):
@pngafney would you mind trying the way above?
@santaklouse commented on GitHub (Apr 12, 2022):
same for me, all programs that works with disk freezes after mount.
How can i umount/kill it?
@pngafney commented on GitHub (Apr 18, 2022):
Sorry for the delay but I just tried with the _netdev option and I get the exact same behavior. I'm not making my connections automatically so my network is for sure 100% up before I try the mappings.
@NoraGithub commented on GitHub (May 2, 2022):
cc @ggtakec
@ggtakec commented on GitHub (May 16, 2022):
I'm sorry for my reply late, and thank you for your confirmation.
Thanks to you, I found that _netdev doesn't change this system result.
I've looked into this error, but with Objective-C initialization and fork() may be involved.
I found a workaround from several sites.
If you can try it, try starting s3fs(without the -f option) by setting the following environment variables:
export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YESI hope that this environment variable may avoid this error.
@showxu commented on GitHub (Jul 1, 2022):
this actually work, what is underlying reason?
I observed that the chmod is changed to drwxrwxrwx and chgrp, chown become the same as other folder on hard dirk. When OBJC_DISABLE_INITIALIZE_FORK_SAFETY flag is unset, that was root
@gaul commented on GitHub (Jul 1, 2022):
Does the
forkcall come from libfuse daemonizing? Can you try runnings3fs -fas an additional workaround?@ggtakec commented on GitHub (Jul 6, 2022):
I haven't yet determined if this is a problem with s3fs itself or a problem on the fuse library.
(still my imagination) It may be in the initialization of the curl library in s3fs, that is called after fork.
And I think there are other parts that need to be checked besides curl initializing.
I haven't been able to reproduce this problem yet, so it's difficult to fix now.
But I think that by disabling error detection by the
OBJC_DISABLE_INITIALIZE_FORK_SAFETYenvironment, the operation will be stable.(I think maybe this error only points out a danger about initializing after fork in Objective-C. Of course, I think the cause of the problem needs to be fixed, but it will still take some time to investigate.)
@nhm91135 commented on GitHub (Jul 30, 2022):
I had this same problem as described by OP.
But I noticed that @gaul had asked for another test.
Using the the suggestion from @gaul s3fs -f , This also works, no crash, no slowness. So that is another workaround, and is Perhaps a Better workaround than using
export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YESas there are implications for other programs if they see that ENV variable.macOS Montery Version 12.5 updated today, MBP 15" 2017
macFUSE 4.4.0 updated yesterday
s3fs version V1.91 installed today
There is a problem Dragging files in Finder; I get error message that it can't be copied because there isn't enough free space. (see attached)
I can copy the file on the CLI no problems, it's just finder, perhaps this is unrelated.
@leszekeljasz commented on GitHub (Aug 16, 2022):
I'm having the same issue with macFUSE v4.4.0 and s3fs v1.91 on MacOS Monterey 12.5, and I can confirm running
s3fsin foreground or with theOBJC_DISABLE_INITIALIZE_FORK_SAFETY=YESworks around the problem.