-
Notifications
You must be signed in to change notification settings - Fork 441
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
Go programs stored on GCS via gcsfuse crash at launch #562
Comments
I guess the above based on the following log (extracted from the above log)
Also, |
This is the same issue as #288. |
@lezh Would you clarify why this is considered same as #288? This issue happens since go1.14 which was released in Feb, 2020, but #288 was reported in 2018. As far as I understand, the read request is interrupted because the Linux kernel received some signal (SIGURG from the go runtime, I think). That seems a different cause from #288. |
I get the same error in 0.38 sometimes, is there any progress? |
Running any kind of code from gcsfuse mount is not a supported use-case. |
Update: As of version 2.1 on 23-May-2024, we now offers enhanced control over how GCSfuse responds to interruptions during file system operations. You can configure GCSFuse to ignore interruptions during file system operations via CLI using --ignore-interrupts flag (disabled by default) or via config-file using the following config:
Please try with this flag |
With GCSfuse v2.3 this is now enabled by default. Thank you all for testing and providing feedback! |
When I run a Go program on the gcs filesystem using gcsfuse (commit 70695b5, the tip of
master
branch), the program crashes at launch. The gcsfuse and the Go program are executed on a Google Cloud instance. The program is compiled with go1.17.2. The reproducing steps are described here and here. The stack trace is shown here. I first filed the issue in golang/go#48997, @randall77 reproduced the issue on his Google Cloud instance as well.Below is the output of
/tmp/bin/gcsfuse -o rw -file-mode=777 -dir-mode=777 --debug_fuse --debug_gcs --foreground my_bucket ~/gcs
, assuming we have a GCS bucket,my_bucket
:Notes
GODEBUG=asyncpreemptoff=1
(disables the asynchronous preemption introduced in go1.14)./usr/bin/python3.7
) in the gcs filesystem.The text was updated successfully, but these errors were encountered: