MacOS – Unable to mount an NFS share

macosNetworknfs

I'm trying to access my (Synology) NAS share through NFS and always get the same issue.

First, I activated NFS support in my NAS:
NAS activated

Then I set the permissions on the NAS:
NAS NFS permissions

My MBP has the IP 192.168.1.109.
From there it seems OK. a showmount -e 192.168.1.2 shows the list:
Exports list on 192.168.1.2: /volume1/video 192.168.1.109 /volume1/homes 192.168.1.109

But unfortunately, my mount always fails:
GroundControl:/ ludo$ sudo mount -t nfs -o rw 192.168.1.2:/volume1/homes /Volumes/home mount_nfs: can't mount /volume1/homes from 192.168.1.2 onto /Volumes/home: Operation not permitted

The /Volume/home directory is created upfront.

Trying with a non-existing share on the NAS, for example /volume1/qwerty gives a Permission denied error, which is OK.
But what is this Operation not permitted error?

Trying through DiskUtils>NFS Mounts gives the same result.

What did I miss?

Best Answer

Or just use the "resvport" option with the mount command.

mount -o resvport nasbox.local.com:/try /mnt

Related Solutions

Mount NFS share in /Volumes as a drive

There is a boring, technical explanation (which I cannot find right now) for this behavior . I worked around it by adding /Volumes to the Favorites section in the Finder's sidebar

enter image description here

MacOS – Mount Linux NFS share on Mountain Lion 10.8.5

I have spent quite a bit of time figuring out automounts of NFS shares in OS X...

Somewhere along the line, Apple decided allowing mounts directly into /Volumes should not be possible:

/etc/auto_master (see last line):

#
# Automounter master map
#
+auto_master        # Use directory service
/net            -hosts      -nobrowse,hidefromfinder,nosuid
/home           auto_home   -nobrowse,hidefromfinder
/Network/Servers    -fstab
/-          -static
/-          auto_nfs    -nobrowse,nosuid

/etc/auto_nfs (this is all one line):

/Volumes/my_mount    -fstype=nfs,noowners,nolockd,noresvport,hard,bg,intr,rw,tcp,nfc nfs://192.168.1.1:/exports/my_share

This will not work (anymore!) though it "should".

$ sudo automount -cv
...
automount: /Volumes/my_mount: mountpoint unavailable

What's the solution?

It's so easy my jaw dropped when I figured it out. Basically, we trick OS X into thinking we're mounting * somewhere else. *

When you're talking about paths in just about any environment, the root folder is the highest path you can reach, whether it's C:\ (windows) or / (*nix)

When you're at this path, attempting to reach the parent path, via .. will keep you at the root path.

For example: /../../../../ is still just /

By now, a few of you have already figured it out.

TL;DR / Solution:

Change your /etc/auto_nfs config from (this is all one line):

/Volumes/my_mount    -fstype=nfs,noowners,nolockd,noresvport,hard,bg,intr,rw,tcp,nfc nfs://192.168.1.1:/exports/my_share

To (this is all one line):

/../Volumes/my_mount    -fstype=nfs,noowners,nolockd,noresvport,hard,bg,intr,rw,tcp,nfc nfs://192.168.1.1:/exports/my_share

And re-run the automounter:

$ sudo automount -cv
...
automount: /Volumes/my_mount: mounted

..... there you go! Technically /../Volumes is still /Volumes, but the automounter does not see things that way ;)

This configuration persists the mount across restarts, and creates the mountpoint automatically.