mount: after closing "minikube mount" can not re-mount to same destination

[medyagh]

to reproduce I tried mounting a folder into /tmp2 in minikube and it worked but after that I killed the Mount
and then inside minikube I tried to ssh in and ls that folder, I could see the folder name but I can't go inside it and also it does NOT let me to redo the mount to the same location
I will need to mount to a different place

$ minikube mount ~/.asdf:/tmp2
📁  Mounting host path /Users/medya/.asdf into VM as /tmp2 ...
    ▪ Mount type:   9p
    ▪ User ID:      docker
    ▪ Group ID:     docker
    ▪ Version:      9p2000.L
    ▪ Message Size: 262144
    ▪ Options:      map[]
    ▪ Bind Address: 192.168.106.1:60103
🚀  Userspace file server: ufs starting
✅  Successfully mounted /Users/medya/.asdf to /tmp2

📌  NOTE: This process must stay alive for the mount to be accessible ...
^C🔥  Unmounting /tmp2 ...

❌  Exiting due to MK_INTERRUPTED: Received interrupt signal




$ minikube ssh
                         _             _            
            _         _ ( )           ( )           
  ___ ___  (_)  ___  (_)| |/')  _   _ | |_      __  
/' _ ` _ `\| |/' _ `\| || , <  ( ) ( )| '_`\  /'__`\
| ( ) ( ) || || ( ) || || |\`\ | (_) || |_) )(  ___/
(_) (_) (_)(_)(_) (_)(_)(_) (_)`\___/'(_,__/'`\____)


$ cd /tmp2 
$ ls
ls: cannot open directory '.': Input/output error
$ rm -rf tmp2
rm: cannot remove 'tmp1': Input/output error

trying to mount to same place after I Killed the "mount"

$ minikube mount ~/.asdf:/tmp2
📁  Mounting host path /Users/medya/.asdf into VM as /tmp2 ...
    ▪ Mount type:   9p
    ▪ User ID:      docker
    ▪ Group ID:     docker
    ▪ Version:      9p2000.L
    ▪ Message Size: 262144
    ▪ Options:      map[]
    ▪ Bind Address: 192.168.106.1:60242
🚀  Userspace file server: ufs starting

❌  Exiting due to GUEST_MOUNT: mount failed: create folder pre-mount: /bin/bash -c "sudo mkdir -p /tmp2": Process exited with status 1
stdout:

stderr:
mkdir: cannot stat '/tmp2': Input/output error

so it seems like our Clean Up Process is not good

here is the verbose logs for when I hit the Ctrl+c to kill the mount process

✅  Successfully mounted /Users/medya/.asdf to /tmp4
I0716 11:59:47.860670   22369 out.go:201] 

I0716 11:59:47.867672   22369 out.go:177] 📌  NOTE: This process must stay alive for the mount to be accessible ...
📌  NOTE: This process must stay alive for the mount to be accessible ...

^CI0716 11:59:55.215420   22369 out.go:177] 🔥  Unmounting /tmp4 ...
🔥  Unmounting /tmp4 ...
I0716 11:59:55.221353   22369 ssh_runner.go:195] Run: /bin/bash -c "[ "x$(findmnt -T /tmp4 | grep /tmp4)" != "x" ] && sudo umount -f /tmp4 || echo "
I0716 11:59:55.230055   22369 mount.go:180] unmount for /tmp4 ran successfully
I0716 11:59:55.230270   22369 lock.go:35] WriteFile acquiring /Users/medya/.minikube/profiles/minikube/.mount-process: {Name:mke6448d2cea86cbefb8461d3a8ed02c900b3f4e Clock:{} Delay:500ms Timeout:1m0s Cancel:<nil>}
I0716 11:59:55.234368   22369 out.go:201] 

W0716 11:59:55.238386   22369 out.go:270] ❌  Exiting due to MK_INTERRUPTED: Received interrupt signal
❌  Exiting due to MK_INTERRUPTED: Received interrupt signal