macOS NFS

Sysadmins OS
, , , ,
1

Sometimes the obvious isn’t obvious.

Connecting macOS workstations to Network File System (NFS) shares is sometimes less convenient than Server Message Block (SMB/CIFS) shares.

If you’re connecting your macOS workstation to your NAS you may experience problems with flame if you are not using NFS.

Here is a reasonably simple guide for one method of enabling NFS connections from your macOS flame to your NAS.

  1. Enable a static IP address for your NAS (This is defined in your router settings)

  2. Define a shared directory on your NAS and enable NFS sharing.

  3. Edit the auto_master file:
    Open the Terminal on your macOS workstation and edit the /etc/auto_master file using a text editor like nano or vi:

    sudo nano /etc/auto_master

    Add a line at the end of the file to reference a new map file:

    /-    auto_nfs

  4. Create the auto_nfs map file:
    Create a new file called /etc/auto_nfs and define the mount points and corresponding NFS shares. For example:

    sudo nano /etc/auto_nfs

    Add the following lines to the file, replacing your-nfs-server and your-share with the appropriate values:

    /path/to/mount/point    -fstype=nfs,rw,nfsvers=4    nfs://your-nfs-server:/path/to/your-share

  5. Reload the autofs service:
    After editing the files, reload the autofs service to apply the changes:

    sudo automount -vc

This setup should automatically mount the NFS shares when they are accessed, but in some instances, you may need to create

/path/to/mount/point

11 Likes
2

EXTREMELY related..

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Unable-to-edit-etc-exports-and-auto-master-file-on-Mac-after-Flame-2023-2-updates.html

3

insanity…. Flame is such a convoluted ecosystems. I’ve been yelling for a decade, that it needs to behave like “just app”, similar to Nuke and ever other software out there. Resolve somehow plays nicely with the world.

3 Likes
4

been sitting here trying to get macos to accept that i want a larger read and writebuffer for NFS than 32K but ITS REFUSING TO LISTEN TO ME !!! :smiley:

Resolve project server setup : 10 minutes in docker

Flame Project server; a lifetime of fun

2 Likes
5

It so needs to be this!

6

Those instruction don’t work. Or to rephrase, they haven’t for me for exports. I gave up trying till I had more time to investigate.

Just a heads up…

7

same.

also /host is protected and autodesk doesnt want me to use nfs v4 for whatever reason.

8

I’ve used this for years it just makes life easier.

5 Likes
9

Same for me.. haven’t been able to get my Mac and Linux box to ‘talk’ .. gave up, too busy to be doing the reluctant sysadmin thing.. oh.. and back in the day I had no problem getting machines to talk, even in the irix days when using sdp over infiniband.. :person_shrugging:

2 Likes
10

Everytime my iMac Flame was connected to the server via NFS it was a disaster at my old job, so many permission errors, weird disconnects… :confused:

11

Posting this here as well, since I eventually DID get it working.

2 Likes
12

Thanks Chris,

I had been missing the synthetic.conf everytime I attempted this, but I guess its needed for SIP.

I ran into an issue where my Linux box was exporting shares from /Volumes, and macOS flagged that as a security risk. I fixed it by changing my /etc/exports path from /Volumes/share_dir to /mnt/share_dir so macOS would allow the mount.

13

Another gotcha: if you’re mounting with NFS from the terminal, you must include resvport in the mount options.

Example:

sudo mount -t nfs -o resvport,rw yourserver:/mnt/share /mnt/share

14
2 Likes
15

@mikeparsons - agreed. marcel is a genius.

1 Like