Unmount the directory which is mounted by sshfs in Mac

MacosSshfsUmount

Macos Problem Overview


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?

Macos Solutions


Solution 1 - Macos

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 ...

Solution 2 - Macos

Don't use umount.

Use

fusermount -u PATH

Solution 3 - Macos

sudo diskutil unmount force PATH 

Works every time :)
Notice the force flag

Solution 4 - Macos

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.)

Solution 5 - Macos

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

Solution 6 - Macos

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.

Solution 7 - Macos

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.

Solution 8 - Macos

In my case (Mac OS Mojave), the key is to use the full path

$umount -f /Volumnes/fullpath/folder

Solution 9 - Macos

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

Solution 10 - Macos

If you have a problems with fusermount command you can kill the process :

> ps -ax | grep "sshfs"

Solution 11 - Macos

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.

Solution 12 - Macos

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.

Solution 13 - Macos

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

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionwaitingkuoView Question on Stackoverflow
Solution 1 - MacosTimur MingulovView Answer on Stackoverflow
Solution 2 - MacospalswimView Answer on Stackoverflow
Solution 3 - MacosMuhsinFatihView Answer on Stackoverflow
Solution 4 - MacosMatt HealyView Answer on Stackoverflow
Solution 5 - MacoshjfitzView Answer on Stackoverflow
Solution 6 - MacoscasewView Answer on Stackoverflow
Solution 7 - MacosErlend Magnus ViggenView Answer on Stackoverflow
Solution 8 - MacoslxyView Answer on Stackoverflow
Solution 9 - MacosChristian ButzkeView Answer on Stackoverflow
Solution 10 - Macosuser3396875View Answer on Stackoverflow
Solution 11 - MacosvikingbenView Answer on Stackoverflow
Solution 12 - MacosmarvinView Answer on Stackoverflow
Solution 13 - MacosottoView Answer on Stackoverflow