-
Notifications
You must be signed in to change notification settings - Fork 271
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
Better mount error message? #170
Comments
Right now, the mount helper stdout/stderr are logged but not captured in the error. Logging has been more helpful for me as there's too many scenarios where the mount helper hangs, and if its stdout/stderr were just buffered somewhere, nothing would ever be displayed. Lines 98 to 99 in 371fbbd
So, with that in mind -- you should have still seen whatever complaint the mount helper had. What actually happened, and how can I reproduce it? |
Not reproducable unfortunately, and the case I encoutered was a failure in loading the kext: Here is something that might be better: |
I'd like this. While fuse.Mount prints something, I want to return the message to my myfs.mount handler app rather than just "fusermount: exit status 1" I want what's logged to stdout which is "fusermount: failed to access mountpoint /my/path: Permission denied" |
The error message returned from mount failure here can be "exit status 255":
https://github.com/bazil/fuse/blob/master/fuse.go#L173
This isn't super helpful in identifying the mount problem. Perhaps it should pass along more context about what exited with that status and any output from running mount or load which includes what fuse reported went wrong.
The text was updated successfully, but these errors were encountered: