-
Notifications
You must be signed in to change notification settings - Fork 187
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
Spontaneous(?) silent unmount #1148
Comments
@evanfields thanks for opening the issue, I have a few suggestions.
Thanks! |
Hey @dannycjones thanks for the swift response!
My bash profile has:
I stop the instance overnight so nothing right now (fresh start), will report back if there's something there that doesn't look like the above logs. I've configured debug logging to a file and will share it once I see another unmount. Thanks! |
@dannycjones first unmount didn't take long today 🤷♂️ dmesg:
Slightly redacted log file: attached |
Sorry for the delayed response - are you still impacted by this issue? Reviewing the Mountpoint logs, it appears to be unmounting cleanly due to it being requested to unmount. I see in the original logs that it appeared to be unmounted by systemd.
I think to further debug, we'd need to dig into why systemd was deactivating that unit. From our side, Mountpoint appears to be working fine. |
No worries @dannycjones and thanks for the response. Yep, I'm still affected by the issue. Let me know any suggestions on what to look for or where to look for it! |
There's a few areas here.
|
Mountpoint for Amazon S3 version
mount-s3 1.10.0
AWS Region
us-east-1
Describe the running environment
mount-s3
command is in my.bash_profile
Mountpoint options
What happened?
I do most of my development work SSH'd into an EC2 instance. I have a
mount-s3
command in my~/.bash_profile
to mount my bucket on login. About twice per working day I find that my bucket is no longer mounted.mount-s3
command works just fine for another few hours, until another spontaneous unmount.Relevant log output
The text was updated successfully, but these errors were encountered: