I'm having issues with automount with my NFS shares after upgrading to MacOS Monterey 12.3.1. /etc/auto_master:

`
#
# Automounter master map
#
/System/Volumes/Data/mnt auto_mounts
+auto_master            # Use directory service
#/net                   -hosts          -nobrowse,hidefromfinder,nosuid
/home                   auto_home       -nobrowse,hidefromfinder
/Network/Servers        -fstab
/-                      -static

` /etc/auto_mounts

`
nas         10.17.24.105:/homes/mynas

`

`
$ sudo automount -vc
automount: /System/Volumes/Data/mnt mounted
automount: /System/Volumes/Data/home updated (/home -> /System/Volumes/Data/home)
automount: no unmounts
$ ls -l /System/Volumes/Data/mnt/
total 0
ls: fts_read: Input/output error

` Any ideas? I have already tried a bunch of things, including manually mounting the shares with mount -t nfs.

Does anyone know why files are showing nobody:nobody ownership using Kerberos and secure NFSV4 with MacOS? kinit user mount -t nfs -o vers=4,sec=krb5 IP:/export/nfs-test /Volumes/export/mnt I note that, if I create a file on the mount, on MacOS it is owned by nobody, but when I check on the NFSv4 server, it has the correct ownership user. I'm not sure if this is some relationship between idmapd, MacOS NFSv4 implementation or perhaps some infrastructure misconfiguration. I have a DNS server, however LDAP isn't configured. Perhaps there need to be some GID/UID mapping on MacOS available via LDAP?

On macOS Sequoia 15.5, I am unable to mount a NFS share from a Debian server. And showmount doesn't work, i.e.:

$ showmount -e myServer

showmount: Cannot retrieve info from host: omv: RPC: Program not registered

My /etc/nfs.conf file looks like this:

nfs.client.mount.options = nfssvers=3,async,tcp,rw,rdirplus,rsize=65536,wsize=65536,locallocks

And rpcinfo -p myServer on the mac client looks like this:

program vers proto   port
    100000    4   tcp    111  rpcbind
    100000    3   tcp    111  rpcbind
    100000    2   tcp    111  rpcbind
    100000    4   udp    111  rpcbind
    100000    3   udp    111  rpcbind
    100000    2   udp    111  rpcbind
    100005    3   udp  42419  mountd
    100005    3   tcp  54335  mountd
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    3   tcp   2049  nfs_acl
    100003    3   udp   2049  nfs
    100227    3   udp   2049  nfs_acl
    100021    1   udp  51022  nlockmgr
    100021    3   udp  51022  nlockmgr
    100021    4   udp  51022  nlockmgr
    100021    1   tcp  44773  nlockmgr
    100021    3   tcp  44773  nlockmgr
    100021    4   tcp  44773  nlockmgr
    100024    1   udp  42149  status
    100024    1   tcp  43701  status

Also, /etc/exports on the server looks like this:

/export/my-share-2025-01 10.0.1.0/24(fsid=5c62a167-aba5-4115-b68c-e5ed8d459d34,rw,crossmnt,insecure,nroot_squash,async,no_subtree_check,anonuid=502,anongid=20)
/export 10.0.1.0/24(ro,fsid=0,root_squash,subtree_check)

How can I troubleshoot and fix this?

I have a few NAS/UNRAID servers that I connected to from my macOS (Ventura) client over SMB, but I'm currently swapping over to NFS. From the command line, things are fine and work as expected. However, on my Desktop, the custom icons I had for the shares/volumes are gone (replaced with the default), and I can't seem to put them back using the technique outlined here , for example. I've tried ICNS & PNG files, and these worked just fine with SMB (and still do). Are custom Volume icons not supported for NFS?

I have a directory on my Mac shared via NFS. Here is the exports entry: /Volumes/Data01/Projects -alldirs –mapall=dpatterson –network 172.24.0.0 –mask 255.255.0.0 I am unable to mount it on the Proxmox host. This is what I get when I attempt to mount it:

# mount -vvvv macpro-2019.dpc:/Volumes/Data01/Projects /mnt/Projects
mount.nfs: timeout set for Fri Jun  6 13:50:24 2025
mount.nfs: trying text-based options 'vers=4.2,addr=172.24.112.10,clientaddr=172.24.252.201'
mount.nfs: mount(2): Input/output error
mount.nfs: mount system call failed

The /Volumes/Data01/Projects directory is owned by dpatterson. I've enabled full disk access for nfsd on the Mac. The Proxmox server is definitely within the 172.24.0.0/16 network Running MacOS Sequoia 15.3 Running Proxmox 8.4.1 TIA

In macOS Monterey, when I quick look files located on NFS shares, the modify date/time has been changed. How can I prevent this?

I've just bought an M2 MB Air to replaced my aging intel macbook. I've got a home server running Ubuntu 22.04 and if provides NFSv4 mounts. My UID under Ubuntu is 1000. When I tryed chaning my UID on my M2 machine it had a meltdown. It wouldnt let me access anything and kept telling me that it couldnt verify icloud etc. I assume that this is becase the UIDs of some of the folders in ~/Library were still set to 501 (when I tried to chnage them to 1000 I got permission refused errors). This works fine on my old intel machine. I ended up having to erase and reinstall on the M2 machine (and it was hard work to get this to happen -- a few times I would get errors trying to erase and reinstall). I assume that Ventura on an M2 locks the UIDs of certain folders as an extra security? Is it possible to change your UID on an M2 Mac (setting up Kerbros on a home network seems overkill).

With this command from terminal I can succesfully connect to NFS share, but how to automate this? sudo mount -t nfs -o nfsvers=3,proto=tcp,resvport 192.168.x.x:/nfsshare /Users/xxx/nfsshare Until now, I was able to connect to NFSv4 shares from Finder's Connect To Server option and then to drag that volume to Login Items in User section of System Preferences, but I had to downgrade Ubuntu's NFS support to v3, because v4 causes freezing of the whole NFS server machine. The same technique for automatic launch of shares is not working with NFSv3. Already tried this: https://lowhangingfruit.dev/2019-10-21/automount-nfs-on-macos/ , no luck. Anyone can help me? Thanks!

On my old Mac mini (Mojave), I would add something like "/foo -rw 192.168.0.99" to /etc/exports, restart nfsd, and then I could connect from that IP to the Mac. On my new Mac mini (Sequoia), nfsd is there and running, but there's no /etc/exports. I tried creating it and then doing the above, but when I do showmount I get nothing: matt@mattmini2 ~ % showmount -e Exports list on localhost: I'm assuming there's a new method for doing this in Sequoia, but if so my googling is failing me. Can anyone help?

I have my Macbook Pro (MacOS Mojave) connecting to an NFS share on a Linux machine directly connected via Thunderbolt with jumbo frames. Testing with iperf3, I can do ~14 Gbps (~1.8 GBps) over the connection, so I expect that network is not the bottleneck. Here is the /etc/exports:

/srv/share         169.254.0.*(rw,sync,insecure,rw,all_squash,anonuid=1000,anongid=1000,no_subtree_check)

Doing some simple testing with dd, here is what I see: ### Direct to disk on the server (~800MB/s)

~$ dd if=/dev/zero of=/tmp/testfile bs=5120 count=100000
100000+0 records in
100000+0 records out
512000000 bytes (512 MB, 488 MiB) copied, 0.62477 s, 820 MB/s

### NFS from the server (~660 MB/s) I connected a client on the server to see how it performed with a Linux client and taking the network out of the equation.

$ sudo mount -t nfs -o rw 169.254.0.1:/srv/share /tmp/share
$ nfsstat -m
/tmp/share from 169.254.0.1:/srv/share
 Flags:	rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=169.254.0.1,local_lock=none,addr=169.254.0.1
$ dd if=/dev/zero of=/tmp/share/test_file bs=5120 count=100000
100000+0 records in
100000+0 records out
512000000 bytes (512 MB, 488 MiB) copied, 0.76516 s, 669 MB/s

### From Macbook Pro over Thunderbolt (~150MBps) I tried to match the default NFS client connection from Linux, but the Mac client doesn't support the same options. I've tried vers=3 and even async, but am never able to get it much faster than this.

$ sudo mount -t nfs -o rw,vers=4,rsize=1048576,wsize=1048576,hard,proto=tcp,timeo=600,retrans=2,sec=sys 169.254.0.1:/srv/share /srv/share
$ nfsstat -m
/srv/share from 169.254.0.1:/srv/share
  -- Original mount options:
     General mount flags: 0x0
     NFS parameters: vers=4,proto=tcp,hard,rsize=1048576,wsize=1048576,timeo=600,retrans=2,sec=sys
     File system locations:
       /srv/share @ 169.254.0.1 (169.254.0.1)
  -- Current mount parameters:
     General mount flags: 0x4000000 multilabel
     NFS parameters: vers=4.0,proto=tcp,port=2049,hard,nointr,noresvport,callback,negnamecache,nonamedattr,noacl,noaclonly,locks,noquota,rsize=65536,wsize=65536,readahead=16,dsize=32768,nordirplus,nodumbtimr,timeo=600,maxgroups=16,acregmin=5,acregmax=60,acdirmin=5,acdirmax=60,nomutejukebox,noephemeral,nonfc,sec=sys
     File system locations:
       /srv/share @ 169.254.0.1 (169.254.0.1)
     Status flags: 0x0
$ dd if=/dev/zero of=/srv/share/testfile bs=5120 count=10000
10000+0 records in
10000+0 records out
51200000 bytes transferred in 0.337533 secs (151688873 bytes/sec)

--- Given how fast the network is, it seems like I should be able to get 3-4x the speeds I'm seeing from the Mac. How can I improve the performance?

When I'm reading this guide it seems to be quite straightforward. http://support.apple.com/kb/PH18705?viewlocale=en_US But I was expecting to be typing the ip address. I don't understand what they mean by nfs://DNSname/pathname DNSname and pathname. Can someone elaborate? (I'm trying to connect to my seagate business storage nas)

On my Mac Studio I have three folders that I use as mount points for NFS shares. I manage the NFS mounts with NFS Manager. Up until recently (I suspect the update to Sonoma 14.4, but I'm not sure) everything worked OK, though I had to mount the shares explicitly from within NFS Manager. Now the shares seem to be mounted automatically (whether at boot or on log-in, I cannot say). But their contents are not visible. When I try to tell NFS Manager to mount them it does nothing and produces no error message. And the contents remain invisible. Interestingly, it appears that macOS uses low numbered inodes for mount points with a mounted share. This confused me at first. My original question was based on a complete misunderstanding of the meaning of low-numbered inodes. Somehow, in one of the updates to Sonoma, Something Changed and the folders were mounted but their contents not visible. I solved this by deleting the definitions in NFS Manager and redefining them. Now it all works again.

I already figured a way, and it kinda works, but it just feels wrong. Is there a more proper way to do it? I recently upgraded from Mojave to Ventura and suddenly realized I lost all my root folders, and I'm no longer able to create one. I dug through Q&A and found info about /etc/synthetic.conf - but it could easily create symlinks only, and I found out that typescript-eslint for example cannot work with root symlinks, it needs real directory. My later research resulted in either local NFS share or macFUSE bindfs. I tried first, because it is already installed and seems easier. I had /work and /data directories and I moved them to /opt/work and /opt/data. Created NFS share: - /etc/exports

/opt/data /opt/work 127.0.0.1 ::1

- sudo launchctl start com.apple.rpcbind - sudo nfsd enable - sudo nfsd stop - sudo nfsd start Created empty mount points in root directory: - /etc/synthetic.conf

data
work

Restarted, checked, mount points are created, and showmount -e is ok. Manual NFS mounting is ok too sudo mount -t nfs 127.0.0.1:/opt/data /data, checked, sudo umount /data Now I'm trying to mount these on startup. ### First I tried /etc/fstab - it is not mounted on restart, and sudo automount -cv shows weird error automount: /data points to unexpected location /data, instead of /System/Volumes/Data/data and it also creates symlink /System/Volumes/Data/data -> /opt/data. Root /data remains empty. Here is my part of /etc/fstab

127.0.0.1:/opt/data /data nfs rw,actimeo=1,hard,bg
127.0.0.1:/opt/work /work nfs rw,actimeo=1,hard,bg

### Second I tried /etc/auto_master. I got the same error as above, and after a lot of trial and error I came to this solution: - my part of /etc/auto_master

/-			/etc/auto_nfs

- /etc/auto_nfs

/System/Volumes/Data/../../../data -fstype=nfs,rw,actimeo=1,hard,bg 127.0.0.1:/opt/data
/System/Volumes/Data/../../../work -fstype=nfs,rw,actimeo=1,hard,bg 127.0.0.1:/opt/work

It works, persisted between reboots and sudo automount -cv shows proper

automount: /System/Volumes/Data/home updated (/home -> /System/Volumes/Data/home)
automount: /data updated
automount: /work updated
automount: no unmounts

Is there a proper not hacky way to do this? Why it disallows to mount at root, and expects /System/Volumes/Data? I found some info that you can do data /System/Volumes/Data/data in /etc/synthetic.conf and then mount NFS to /System/Volumes/Data/data - but again - there will be symlink at root.

I've ran out of disk space (heh). So, I cleverly mounted some shares via NFS (which is blindingly fast compared to any other type of file sharing, thanks to the advanced support macOS has for NFSv4, built into the kernel itself). For trivial things (music, video...) this works nicely. The issue I've got is simply that some applications I have (games!!), to run from a NFS share, they need it to be mounted as **case-insensitive**, but NFS, by default, mounts filesystems as **case-sensitive**: On Synology (DS218play, DSM 7.2.1-69057 Update 3) everything is (supposedly) handled via the Shared Folder option in the Control Panel: which, in turn, produces the following:

$ sudo cat /etc/exports
/volume1/movies	10.1.1.0/24(rw,async,no_wdelay,crossmnt,insecure,all_squash,insecure_locks,sec=sys,anonuid=1024,anongid=100)
/volume1/music	10.1.1.0/24(rw,async,no_wdelay,crossmnt,insecure,all_squash,insecure_locks,sec=sys,anonuid=1024,anongid=100)
... etc for other shares...

(10.1.1.0/24 being in this example the IP range for my home network) On the macOS (Big Sur), I mount the NFS shares via the Finder, using **Go** > **Connect to Server...** which, in my experience, is the best way to get them to work (believe me, I've tried many alternatives explained thoroughly on several places, including here on Ask Different). I make them persistent simply by dragging them on the **Login Items** tab for my user under **Users & Accounts**. The (working) result shows up as:

$ mount
synology.local:/volume1/music on /Volumes/music (nfs, nodev, nosuid, mounted by gwyneth)
synology.local:/volume1/movies on /Volumes/movies (nfs, nodev, nosuid, mounted by gwyneth)
... etc for other shares...

So far, so good, and this essentially works for everything that is fine with case-sensitive mounts — the default in the Unix world, after all. But now I wish to tweak the parameters to get those mounts to be case-*in*sensitive! Mind you, I'm fine in having such tweaks either on the side of macOS or on the Synology; even a "temporary" solution (one that doesn't survive reboots, upgrades, etc.) would go a long, long way to get things running. But I have taken a look at similar questions such as: * https://apple.stackexchange.com/questions/124118/does-mavericks-have-a-gui-for-nfs-mounts-as-in-previous-os-x-versions * https://apple.stackexchange.com/questions/19466/unable-to-mount-an-nfs-share or even * https://community.synology.com/enu/forum/1/post/140201 (no solution to a similar issue regarding case sensitivity) * https://www.truenas.com/community/threads/how-to-manually-mount-nfs-on-macos-monterey.104377/ (for TrueNAS running Ubuntu, _not_ Synology) * https://github.com/owncloud/core/issues/25372 (again, different platform, this time ownCloud — the issue was acknowledged to exist, but it apparently has no solution) One wild idea seems to sugggest that the NFS filesystem ought to be mounted as a _sparse_ disk image (just like Time Machine does!): - https://wildcardcorp.com/blogs/making-vagrant-virtualbox-nfs-less-painful-with-sparse-disk-images This _seems_ to do the trick, but, alas, seems to be a rather complex way to deal with the whole issue; also, I fear that the potential extra overhead from the sparse filesystem will balance out the benefits of using super-fast NFSv4. Samba shares obviously can be mounted either way, but [I really want to use NFS](https://www.bdrsuite.com/blog/nfs-vs-smb-whats-the-difference/) : * https://superuser.com/questions/713798/case-insensitivity-issues-on-a-nas-connected-to-from-both-linux-and-windows-ma Similar (not exactly the _same_) issues with case-sensitivity vs. case-insensitive under Windows seem to have been fixed [only last year](https://github.com/microsoft/vscode-cpptools/issues/1994) **by simply using a special parameter to toggle case sensitivity**. Cool! Is there a similar parameter for macOS? (Or Synology DSM?) _Note: I'm aware I might be on a wild-goose chase here; nevertheless, who knows, maybe there **is** a way to override the case-sensivity at some kernel or networking layer, it's just that most people are unwilling to do it, thus the lack of proper replies to this issue._

I am having a problem using NFS connecting to shares **from** a Mac with Catalina and another one with Snow Leopard (don't ask why ;). I just updated to BigSur 11.4 When I use : -fstype=nfs,noowners,nolockd,noresvport,hard,bg,intr,rw,tcp,nfc in /etc/auto_nfs

cd /System/Volumes/Data/NetVolumes/data
-bash: cd: /System/Volumes/Data/NetVolumes/data: Invalid argument

if by other hand I use -fstype=nfs,rw,sync

cd /System/Volumes/Data/NetVolumes/data1
-bash: cd: /System/Volumes/Data/NetVolumes/data1: RPC prog. not avail

Has anyone been able to get a working NFS 4 automount in Mac OS X? I'm desperately trying to find a way to automatically mount a NFS v4 share from my NAS to my MacBook Pro with Mac OS 10.11.6, but keep hitting a kernel panic. Upon boot/login, the automount works perfectly. And I can manually u/mount the share (mount -o nfsvers=4 nas:/nfs/htpc-media /tmp/foobar) without trouble. But when I put my Mac to sleep, I get a [kernel panic](https://support.apple.com/library/content/dam/edam/applecare/images/en_US/osx/panic.png) about 2 seconds after waking it back up. NFS v3 works a *little* better, but it will still occasionally crash after a few wakes. I'd really prefer to run v4 services only. Here's the client setup: - **/etc/auto_master** # # Automounter master map # +auto_master # Use directory service /net -hosts -nobrowse,hidefromfinder,nosuid,nfc /home auto_home -nobrowse,hidefromfinder /Network/Servers -fstab /- -static /- auto_nfs - **/etc/auto_nfs** /nfs/media -fstype=nfs,nfsvers=4,soft,intr nas:/nfs/htpc-media And on the NAS (running Debian Stretch): - **/etc/exports** /nfs/htpc-media *(ro,no_subtree_check,insecure,fsid=1) Stuff I've tried: - turning off firewalls on both ends - using IP addresses instead of hostnames (i.e. 192.168.1.99 instead of nas - rules out DNS issues) - lots of permutations of client mount options - booting Mac OS X into safe mode (rules out kext) - poring through Console to see if there's anything interesting or related - automounting shares from a completely separate server (rules out server misconfiguration) Am I missing something obvious? Any help would be appreciated. Happy to post crash logs if that'd be useful.

I have a strange issue with am Unraid server running NFS shares. Facts: * Running a fresh install of Word on a fresh Mac on a fresh Unraid server * Documents are on an NFS4 network share * The share and documents has all permissions: Read - Write - Execute * I can verify this by using "Get info" on a Word document and see that myself, mygroup and all users have Read and Write. I can also verify directly on server. Documents are 777 (rwx for all) * Ready only is not set on document (as seen from Mac get info) * Locked is not set on document (as seen from Mac get info) Symptoms: * When I open a document located on the share in Word on the Mac - it displays a message that the document is read only and only gives me the option do duplicate it. I can duplicate it fine and save to the network location, but when opening the duplicated document, I get the read only message again. * No other programs are behaving this way on the same share - Excel, Powerpoint etc works fine. I can even open a Word document in a text editor and are able to save it - so if it definitely not read only * If I create a new Word document and save it to this network share - I get the same behaviour - it gets read only * If I map the network share using samba (SMB) protocol instead of NFS, it works fine - issue is only with NFS (but I prefer NFS due to speed & reliability when there are many files) So somehow Word thinks that documents on the network share are read only - while they definitely not are read only. Any ideas?

I'm trying to learn more about NFS, and I'm experimenting by exporting arbitrary volumes on my M1 Air (running Ventura 13.1) and then mounting them. Often, I write a row to my /etc/exports file and then find that nfsd doesn't do what I expect; I believe it's erroring, though I haven't been able to find any error logs. I've carefully read through man 5 exports but even so, what works and what doesn't seems totally arbitrary to me. In all of my experiments, I add a single row to /etc/exports and then run sudo nfsd restart; sleep 3; showmount -e. I've pasted a table of my results so far below. Does anyone know why nfsd is failing to come up, or showmount -e doesn't show any mounts in the indicated cases below? | /etc/exports entry | Result | | --- | --- | | /Users -network=127.0.0.1 -mask=255.0.0.0 | Works | | /Users -network=127.0.0.0 -mask=255.0.0.0 | nfsd won’t start | | /Users -network=127.0.0.1/8 | showmount -e returns nothing | | /Users -mapall=root -network=127.0.0.1 -mask=255.0.0.0 | Works | | /Users -mapall=root:root -network=127.0.0.1 -mask=255.0.0.0 | showmount -e returns nothing | | /Users/m -network=127.0.0.1 -mask=255.0.0.0 | Works | | /Users/m/test -network=127.0.0.1 -mask=255.0.0.0 | Works | | /Users/m/Documents -network=127.0.0.1 -mask=255.0.0.0 | showmount -e returns nothing | N.B. In the cases where I've written "showmount -e returns nothing", the specific output is this:

$ showmount -e
Exports list on localhost:

$

Where I've written "nfsd won't start", the output is:

$ showmount -e
showmount: Cannot retrieve info from host: localhost: RPC: Program not registered

Removing the line and then running sudo nfsd restart seems to fix it in these cases.

In linux, one of the great things you could do (for developers, in particular) was to mount a folder and locally bind it to another folder on the system. This had the advantage over symlinks due do the fact tools like Git didn't detect it as being a different type of node, and you didn't need to remove the original contents. When you were done, you could simple unmount and you were left with the original filesystem contents. However, mount -bind or mount.local don't seem to exist on Mac (as of OS X 10.10.2, Yosemite). How do you go about this?

Mounting an nfs storage is failing today, when it worked fine yesterday. sudo mount -v -o rw storage01:/storage/_shares/ci /System/Volumes/Data/Users/bemehiser/Projects/data/ci mount_nfs: can't mount /storage/_shares/ci from storage01 onto /System/Volumes/Data/Users/bemehiser/Projects/data/ci: Permission denied mount: /System/Volumes/Data/Users/bemehiser/Projects/data/ci failed with 13 I don't think any configurations changed. I never even unmounted the storage between yesterday and today. I've tried unmounting the mount (not mounted), deleting the ci dir and recreating it, checking all the permissions, sudo, no sudo, restarting the entire computer, etc. No dice. The mount works on an older macOS 10.14 vm, but not my macOS 10.15.2 MacBook Pro Any suggestions would be appreciated.