Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.6: Add NFS Mounts using Disk Utility' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.6: Add NFS Mounts using Disk Utility
Authored by: unixer on May 27, '12 08:53:21PM

Hi,
I have been attempting to add my nfs mounts via disk utility for awhile now and it always fails, with an error unable to verify server or whatever.
I can mount the nfs shares via the command line and go connect, but not through disk utility. Does anyone have a solution to this?
OSX 10.6.8

Thanx



[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: Berk on Jun 07, '12 04:37:10PM
I've ran into this before and I see a lot of people having issues with this. I have solved the issue for myself on both 10.6 and 10.7. The issue you are having is with automounted nfs shares and finder. The solution comes with configuration on both the server side and the client side.

Setup:
Server - OpenSuse 11.4 32-bit
Client - OS X 10.6.8

The Solution:

nfs server configuration

This is what my /etc/exports looks like and an explanation of the options.,:

/Media *(fsid=1,crossmnt,rw,insecure,all_squash,async,no_subtree_check,anonuid=1000)

the fsid=1 and crossmnt may be just a suse thing. I work with a lot of Suse (OpenSuse, SLES, and SLED) systems and I have had to put this in all of them, but I haven't when hosting from ubuntu and whatnot.

The rest of the flags are

rw=read/write, insecure allows for ports beyond 1024 to connect to the share

all_squash allows for all users to access and be treated as the owner of the share (I think this is right, either way I had set the flag this way for it to work for me)

async allows for better performance by allowing the server to respond to requests before any changes made by that request have been comitted to stable storage.

no_subtree_check improves performance. I have never had any issues with this affecting my systems before. More info on all of these can always be found on the man page for nfs.

anonuid=1000. 1000 is the user id of the user that owns the nfs share on my server. This makes it so that all requests appear to the server as if UUID 1000 is writing to the share, regardless of who is actually doing the writing.

Client Setup
1) Created a directory for my nfs share to be mounted at:

#mkdir -p /mnt/nfs/Media

2) mount the nfs share

#sudo mount -t nfs -o resvport 192.168.1.50:/Media /mnt/nfs/Media

Share mounted just fine. Everything worked from terminal. I then fired up 2 finder windows and dragged and copied a file from my mac to the nfs share. It let me drop it there. Hopped on my nfs server to make sure and the file opened just fine.

If you want to mount this share at boot everytime do the following:

1) Open Disk Utility

2) File --> NFS Mounts

3) Click the '+' in the bottom left corner

4) Enter the Remote NFS URL. In my case: nfs://192.168.1.50/Media

5) Enter the mount location. Once agian, in my case: /mnt/nfs/Media

6) Click on "Advanced Mount Parameters" and enter "resvport"

7) Verify that you are communicating to the NFS server

8) Save


[ Reply to This | # ]