-
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
fh.reader.ReadAt: readFull: context canceled #402
Comments
I am getting this also. It appears randomly and with a different file each time.
|
a. strace would help find the source of the interrupt |
This is similar to #1016. |
@sethiay Any news on this? I had something similar in the last two days on GKE GoogleCloudPlatform/gcs-fuse-csi-driver#36 |
Hey @bhack, Thanks for reaching out. We suggest to follow up on the GoogleCloudPlatform/gcs-fuse-csi-driver#36. |
Closing the issue as it is transferred to https://github.com/GoogleCloudPlatform/gcs-fuse-csi-driver and is closed there. |
In case this issue is still open, some of the logs look similar to #1016 We recently released GCSFuse v2.1.0 yesterday which supports disabling these interrupts thereby context not getting cancelled. Pls use the "--ignore-interrupts=true" flag when mounting GCSFuse to enable the new behavior. |
I'm using dsub 0.3.7 which uses gcsfuse to mount a Google Storage bucket. Recently, I've started running into a lot of io error messages. I've added some detail on the dsub issue, but it sounds like this is likely more closely related to gcsfuse than dsub so I wanted to start a conversation here.
Is there information about what is happening when we get errors such as:
And, in particular, is this something that we should expect to see frequently? Or is it totally dependent on Google Storage, and is gcsfuse dealing with this as expected? As of now, it seems to occur stochastically, but frequently enough that it's fairly crippling to mount with gcsfuse.
The text was updated successfully, but these errors were encountered: