You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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.
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 runningmount
, and any attempts at interacting with the mount point produced anomalous from error messages to long hangs. Runningumount <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).
The text was updated successfully, but these errors were encountered: