I've installed OSXFUSE
in my mac and used sshfs
to mount a remote directory. Now I would like to unmount it, but can't find the way.
My OS is OSX 10.8 Mountain.
Can anyone help?

- 1,308
- 1
- 12
- 20

- 89,478
- 28
- 112
- 118
-
1This question belongs to SuperUser, although there's already [ssh - How to avoid sshfs freezing? - Super User](https://superuser.com/questions/443878/how-to-avoid-sshfs-freezing) there – user202729 May 12 '22 at 01:58
13 Answers
Try this:
umount -f <absolute pathname to the mount point>
Example:
umount -f /Users/plummie/Documents/stanford
If that doesn't work, try the same command as root:
sudo umount -f ...

- 2,453
- 1
- 15
- 8
-
4Using umount -f left me with broken directory giving error: "bash: cd: directory-name: Transport endpoint is not connected" – peterdemin Dec 09 '13 at 10:16
-
5Note for future use: the command above works just fine on Mavericks. Also, an absolute path isn't necessary. – b. e. hollenbeck Apr 01 '14 at 12:37
-
1
-
-
4Fine on OSX 10.10.4 using `umount -f /Users/me/Documents/there` without sudo – Christiaan Westerbeek Aug 10 '15 at 14:23
-
2
-
Fails on 10.13 with error: `Operation not permitted`. Have to use sudo even for a folder in my homedir. – Mike Lischke Apr 16 '18 at 07:08
-
For me, it did not work when I used a relative path (cd ~/Desktop; umount -f rambo). It said the path was not currently mounted. It worked with a user relative path (umount -f ~/Desktop/rambo) – Fractaly Sep 29 '18 at 02:21
-
This was the only command that worked after my /Volumes/mymount mount point went sour, giving the error message "rm: /Volumes/mymount Device not configured" when trying to sudo rm it. – Johan Fredrik Varen Nov 27 '18 at 08:40
-
Don't use umount
.
Use
fusermount -u PATH

- 11,856
- 6
- 53
- 77
-
9This answer came from @peterdemin in the comment for [another answer](http://stackoverflow.com/a/16674890/393280). – palswim Apr 07 '14 at 19:12
-
53
-
38
-
4the
option works fine under Mac System Version: OS X 10.10.3 even without sudo – ravi.zombie Oct 01 '15 at 20:12 -
8Wasn't getting `umount` to work initially because I thought it was `unmount`—there's no `n`! – George WS May 03 '16 at 06:18
-
4macOS 10.13.4: None of these options have worked for me. "umount: gave me "Resource busy -- try 'diskutil unmount'", and that cmd gave me: "Unmount failed for
". Edit: BUT umount -f – phpN00b May 08 '18 at 18:49did work! -
3This answer is blatantly wrong, [fusermount **does not exist** in the macOS version of sshfs](https://github.com/osxfuse/osxfuse/wiki/FAQ#48-how-should-i-unmount-my-fuse-for-os-x-file-system-i-cannot-find-the-fusermount-program-anywhere) (sshfs FAQ). – Isaiah Norton Oct 05 '18 at 01:42
-
-
1`umount -f /path/to/folder` if receiving `Resource busy` with `umount` and `failed` with `diskutil` (Catalina `10.15.2`). – felipe Feb 07 '20 at 06:39
-
Why? What's wrong with umount. This should not have so many upvotes without a reason! – Octopus Apr 15 '21 at 10:34
sudo diskutil unmount force PATH
Works every time :)
Notice the force
flag

- 1,891
- 2
- 24
- 31
-
1Indeed it works every time . Key is the force option :-) For instance : I was getting the following error with umount mount_osxfuse: mount point /Users/mount/root is itself on a OSXFUSE volume diskutil – irsis Nov 04 '19 at 00:29
-
The only thing that actually worked. It's a puzzle to me that `sodo umount -f` didn't work here... I had zombie volumes from `sshfs` – ddofborg Jul 17 '22 at 10:09
At least in 10.11 (El Capitan), the man page for umount indicates:
Due to the complex and interwoven nature of Mac OS X, umount may fail often. It is recommended that diskutil(1) (as in, "diskutil unmount /mnt") be used instead.
This approach (e.g., "diskutil umount path/to/mount/point") allows me to unmount sshfs-mounted content, and does not require sudo. (And I believe that it should work back through at least 10.8.)

- 171
- 1
- 2
-
3A broken pipe would sometimes leave the volume in a very bad state. In these cases, only ```diskutil unmount force /path/to/mountpoint``` would help for me. – cw' Aug 10 '16 at 08:47
-
1Incidentally, this only works for me if I use `diskutil umount force ...`. Other methods [here](https://github.com/osxfuse/osxfuse/issues/45) as well. – abalter Nov 07 '16 at 11:58
use ps aux | grep sshfs
to find the PID of sshfs (It will be the number next to the username)
Then kill -9 $PID
, if the other solutions don't work

- 399
- 4
- 15
-
Works on OS X 10.11.0, after suspending it and moving to a different network (leaving the mount point with Input/Output errors). umount didn't work, fusermount not installed – RobM Oct 07 '15 at 16:42
-
This worked for me when I ran into a situation where many appps/processes were beachballing/“stuck“-status-in-top/“U”-status-in-ps. Cheers. – Slipp D. Thompson Aug 16 '17 at 07:32
The following worked for me:
hdiutil detach <path to sshfs mount>
Example:
hdiutil detach /Users/user1/sshfs
One can also locate the volume created by sshfs in Finder, right-click, and select Eject. Which is, to the best of my knowledge, the GUI version of the above command.

- 81
- 1
- 1
-
This is something that worked for me without a hitch on macOS Sierra. I suspected this would work flawlessly because on Gui I press the eject button this would be the thing that was happening. – retromuz Nov 09 '16 at 19:42
-
-
Works for me on High Sierrra when the other approaches didn't, but had to add the "-force" option: e.g "hdiutil detach /Users/user1/sshfs -force" – Chris Apr 13 '18 at 21:28
If your problem is that you mounted a network drive with SSHFS, but the ssh connection got cut and you simply cannot remount it because of an error like mount_osxfuse: mount point /Users/your_user/mount_folder is itself on a OSXFUSE volume
, the github user theunsa found a solution that works for me. Quoting his answer:
My current workaround is to:
Find the culprit sshfs process:
$ pgrep -lf sshfs
Kill it:
$ kill -9 <pid_of_sshfs_process>
sudo force unmount the "unavailable" directory:
$ sudo umount -f <mounted_dir>
Remount the now "available" directory with sshfs ... and then tomorrow morning go back to step 1.

- 383
- 3
- 14
Just as reference let me quote the osxfuse FAQ
4.8. How should I unmount my "FUSE for OS X" file system? I cannot find the fusermount program anywhere.
Just use the standard umount command in OS X. You do not need the Linux-specific fusermount with "FUSE for OS X".
As mentioned above, either diskutil unmount
or umount
should work

- 1,080
- 12
- 8
-
Today, homebrew suggests "macFuse" (deciding to stop offering osxfuse) -- using `umount` in my OS X still works with "macFuse" just fine (MacOS 13.4.1) – CrashNeb Aug 17 '23 at 15:29
In my case (Mac OS Mojave), the key is to use the full path
$umount -f /Volumnes/fullpath/folder

- 91
- 3
If you have a problems with fusermount
command you can kill the process :
ps -ax | grep "sshfs"

- 47
- 2
Just for reference I found this worked for me.
diskutil unmount /path/to/directory/
When I used the umount command I got an error that recommended this diskutil command.

- 1,632
- 2
- 24
- 37
You can always do this from finder. Simply navigate to the directory above where the mount is and hit the eject icon over the mounted folder, which will have SSHFS in the name (in the finder). A shortcut to open a folder in the finder from the terminal is
open .
which will open up the current directory in a new finder window. Replace "." with your directory of choice.

- 581
- 5
- 9
if you want to kill all mounted sshfs connections you can use this. I tried it with ubuntu.
ps -ef | grep "sshfs" | awk '{print $2}' | xargs kill -9
I added it to bash_aliases

- 1,815
- 7
- 37
- 63