-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Can't mount or unmount filesystem with legacy mountpoint #5755
Comments
Did you have any mount namespaces with zp0/docker mounted? |
Not intentionally at least. The Docker daemon was stopped but maybe it didn't clean up after itself?
How can I list all mount namespaces on my system? |
I don't know if there's any tool that does that. But you can scan through all process through procfs. |
Also unable to unmount zfs volumes with mountpoint=legacy under Ubuntu 16.04.2. Certain (rsync vs other filesystem) issues cause the process to hang, and it can't be killed because of the mountpoint=legacy setting, which causes "umount -f" to also fail. Toggling mountpoint=/some/path allows the rsync process to be killed after it hangs and so the fs can be unmounted. havent tried "umount -f" with the zf process running. |
Same problem here: I ran a keycloak docker container, stopped it, wanted to restart, and now docker tells me:
Any idea how to solve this? |
System information
Problem
After unmounting a ZFS filesystem sometimes I can't re-mount it. Example:
Workaround
I have experienced this several times and it is somewhat annoying.
The text was updated successfully, but these errors were encountered: