Cannot write to NFS share from macOS Sonoma

Perhaps you've redacted too much there. Originally, you said:

Carsten Nitschke wrote:

auto_master

/Users/xxx/xxx auto_nas -nosuid

and then you posted that screenshot referencing a copy to "downloads".

So, by process of elimination, it seems like the actual mount point is:

/Users/<short user name>/downloads

Is that right? If so, I'm surprised it worked this long.

First of all, both NFS and autofs, either separately or especially together, were deprecated and disavowed by Apple years ago. Whether they work at all, under any conditions, is by pure luck. And I'm not talking Sonoma here. This was back in High Sierra days or earlier. It's been a long, long time.

If you are going to try it, you must have very in-depth, detailed knowledge of how both NFS works on the client and server side, as well as very detailed knowledge of how modern Apple security works. Of those things I just mentioned, only the NFS server side has any documentation of any kind. When it comes to this kind of Apple system software, you just have have some kind of "second sight" or the ability to read the tea leaves between the lines.

One of the things that means it that you must never, ever touch any path that has any kind of exceptional Apple security. The downloads folder is one of those. In fact any folder inside a home directory would qualify.

Try it again with some path outside of the user's home directory. After all, that is how NFS was always designed to work in the first place.

Good luck!

Carsten Nitschke wrote:

Could I kindly ask for your suggestion on how to best have access to NFS folders from my Mac in a way that would actually be supported?

There is no way to use NFS what would be supported. NFS is a relic from another age.

Automount has been actually quite nice until now (it did work). Happy to do it in a differnt way if you have insights.

Start by trying a different mount point. It's just going to be trial and error. Avoid any location that has any kind of extra security. So, at a minimum, if you above assumption about downloads was correct, then use some other folder. Don't use Desktop, Documents, or Library either. If that doesn't work, then try a folder outside of your home directory. If that doesn't work, start looking at permissions. If that doesn't work, look at TCC issues.

Which error message are you getting in client?

Do you see anything in server log?

etresoft wrote:

First of all, both NFS and autofs, either separately or especially together, were deprecated and disavowed by Apple years ago. Whether they work at all, under any conditions, is by pure luck. And I'm not talking Sonoma here. This was back in High Sierra days or earlier. It's been a long, long time.

Really? Do you find that documented somewhere? I don't see any such notice in the few man pages that I checked.

In any case, I never got the memo. I had been (mostly) happily using NFS+automount to access a shared file systems mounted on /Network/{Applications,Library,Users} for over 20 years (most recently using a mobile home directory, explicitly accessing my NFS home via symlinks), until moving from macOS 13 to macOS 14. Things were very broken with the betas though as of 14.2.1 I find things mostly working, except I hit an NFS lockup cosmetically similar to this today when trying to copy a folder from /Network/Users/<myusername>/Applications/ to /Network/Applications using Finder, and I recall previously hitting this now, too, probably on macOS 14 betas.

Take a look at Apple documentation for best way to mount NFS

Servers and shared computers you can connect to on Mac - Apple Support (MT)

There is no way to use NFS what would be supported. NFS is a relic from another age.

Perhaps, but what's the alternative when you have a large disk containing user home directories and other content that you need to share among multiple machines on a home network that includes heterogenous client machines ranging from 1 to 30 years old?

Sure, my situation may be relatively unique, but even for sharing content between a few modern Macs, it seems the alternatives like SMB are not extremely practical; it still seems mostly geared toward ad hoc connections via Finder.