-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 failed: mkdir: cannot create directory '/mnt/data': File exists #4239
Comments
@dionizh can you paste exact command line used? |
Hi I have given the command line above: |
What version of minikube is this with? I feel like v1.0.1 should handle this properly by using
|
It is minikube v1.0.1. |
I can confirm that this happens in v1.1 if a process is still using the old mountpoint. We should output a clearer error when this occurs. To reproduce:
|
Thank you. That does sound like what I did. |
I reproduced this issue, and I would like to provide a PR to fix this issue.
After address 1, the message will be more clearer to point the mount point is busy. @tstromberg any comments? Thanks a lot! BR |
Sounds good. I'd be happy to review any PR that makes the failure reason
more obvious. It may be possible that we can't make umount -f work, but we
can at least do a better job of telling the user why the mount failed.
…On Wed, May 29, 2019, 11:33 PM Francis ***@***.***> wrote:
I reproduced this issue, and I would like to provide a PR to fix this
issue.
Append my investigation & solution here:
1. "|| true" is in the umount command. It will lead to "force Unmount"
will be never called, should be code error.
2. Current "force Unmount" cannot work if mount point is busy.
After address 1, the message will be more clearer to point the mount point
is busy.
Error will be gone for this case if 2 is addressed.
@tstromberg <https://github.com/tstromberg> any comments? Thanks a lot!
BR
-Francis
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4239?email_source=notifications&email_token=AAAYYMBDATI2ZNOWPHBJFKLPX5YL3A5CNFSM4HMBKY32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWRP5QQ#issuecomment-497221314>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAYYMFUJNLL3M43K2COTF3PX5YL3ANCNFSM4HMBKY3Q>
.
|
Thanks @tstromberg PR #4393 wish you could help review, any comments are welcome. |
This issue could be closed by fixes #4393 |
@fenglixa: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
When stopping a minikube mount process with ctrl+C, then try to remount the same disk again, minikube crashed with the following message:
Mounting host path /mnt/scratch/dzhong/redis into VM as /mnt/data ...
o Mount options:
- Type: 9p
- UID: docker
- GID: docker
- Version: 9p2000.L
- MSize: 262144
- Mode: 755 (-rwxr-xr-x)
- Options: map[]
@ Userspace file server: ufs starting
! mount failed: mkdir: cannot create directory '/mnt/data': File exists
: Process exited with status 1
Mount command run is a simple:
minikube mount /mnt/scratch/dzhong/redis:/mnt/data
I have to stop minikube, and start it again, for the mount to work.
Running the latest version of minikube and kubectl on centos7.
thanks
dioni
The text was updated successfully, but these errors were encountered: