NFS sharing broken in Tahoe (and Sequoia)

No one here can speak to what Apple plans to do. “We” are users like you and have no power to implement any suggestions. To have Apple consider your feedback, submit it here:

Feedback - macOS - Apple

Richard Harris2 wrote:

Apple hasn't moved beyond NFS 3.x but 4.2 is very much current and relevant.

Not to Apple. Otherwise, they would support it.

benchmarking NFS throughput against SMB in a heterogenous environment with large numbers of small files will show a 2-3x improvement in throughput with NFS.

You might get some interest from Apple on that front. If you can show that Windows or Linux gets better throughput using NFS than macOS does with SMB, there's a slight (very, very slight) chance that someone at Apple would care. You could improve your chances if you did the demo with iOS. That's what Apple cares about.

Richard Harris2 wrote:

NFS is still provided as a service in MacOS Tahoe. It is therefore reasonable to expect that it should work. Except that it doesn't (up to and including 26.1), and appears to have been broken since at least Sequoia. It doesn't matter whether the share is on an internal SSD or on an external array, or what the underlying FS format is, any mount stops responding after five minutes.

Yes. This has been reported before: NFS broken in Sequoia 15.6 - Apple Community

And SMB is NOT an adequate substitute in many environments, especially data intensive applications, where SMB simply does not deliver the throughput.

So does Apple have any plans to fix this oft-reported bug?

Which bug?

I'm sure that nobody cares about NFS. NFS uses an ancient security model. Even the most convoluted, theoretical security exploits involving Apple make headline news.

But if your SMB throughput isn't sufficient, then that might be something that someone could help with. And it would be something that Apple might take an interest in. I recommend you pursue that course of action.