Skip to content
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

mount remains after TERM #130

Open
gotyaoi opened this issue Oct 28, 2016 · 1 comment
Open

mount remains after TERM #130

gotyaoi opened this issue Oct 28, 2016 · 1 comment

Comments

@gotyaoi
Copy link

gotyaoi commented Oct 28, 2016

So, trying to unmount a bucket, I sent the riofs process a TERM signal using kill <pid>. The riofs process exited fine, but the mount still showed up when running mount, and any attempts at interacting with the mount point produced anomalous from error messages to long hangs. Running umount <mountpoint> returned almost immediately, the mount was gone from the list and everything was normal again.

I've reproduced this on both CentOS 6.8(fuse-2.8.3) and osx 10.11(osxfuse-3.5.2).

@wizzard
Copy link
Member

wizzard commented Oct 29, 2016

Hello, this is a known issue, if the application is killed, then FUSE leaves folder in "mounted" state.
I have handlers for SIGINT / SIGTERM signals, which should unmount folder before exiting, but sometimes (especially on MacOS) it does not work.
Please try to kill RioFS with SIGINT and see if it makes any difference.

If you really need to stop RioFS: try to unmount it first and then kill.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants