Newsroom Update

Beginning in May, a special Today at Apple series titled “Made for Business” will offer small business owners and entrepreneurs free opportunities to learn how Apple products and services can support their growth and success. Learn more >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

NFS issues with finder

Is anyone successfully using NFS to share files to 10.6 or 10.7 clients? If so, can you point me to any documentation or fill me in on any "gotchas" you fought along the way?


I have a Solaris 11 server with ZFS file systems shared out via NFS to a few clients. My other Solaris, RHEL 5 and ubuntu clients work flawlessly with the setup. My only issue is with the Mac clients (Both 10.6 and 10.7)


Mounting the export via the CLI and performing a directory listing work great, however file transfers max out at around 3M per second across an empty gigabit link.

showmount

When trying to mount the share in finder (cmd + K) the mount rarely completes. If it does, opening finder to display the files usually takes minutes regardless of contents.


Is there something I'm missing when it comes to serving NFS up to a Mac? The only thing I have to go by so far is the following reported by syslog


Jan 4 00:55:42 [clientname] kernel[0] <Info>: nfs server [ipaddr]:/storage/homes: lockd not responding

Jan 4 00:55:42 [clientname] KernelEventAgent[44] <Notice>: tid 00000000 received event(s) VQ_NOTRESP (1)

Jan 4 00:55:42 [clientname] KernelEventAgent[44] <Notice>: tid 00000000 type 'nfs', mounted on '/Volumes/homes', from '[ipaddr]:/storage/homes', not responding



Reading those kernel messages one would first think that it's the Solaris box having issues, but as I said before all other clients are working great.


From the OS X clients I've also gathered this info:


[clientname]:log rjanuary$ rpcinfo -u [server] nfs

program 100003 version 2 ready and waiting

program 100003 version 3 ready and waiting


[clientname]:log rjanuary$ rpcinfo -p [server]

program vers proto port

100000 4 tcp 111 portmapper

100000 3 tcp 111 portmapper

100000 2 tcp 111 portmapper

100000 4 udp 111 portmapper

100000 3 udp 111 portmapper

100000 2 udp 111 portmapper

100021 1 udp 4045 nlockmgr

100021 2 udp 4045 nlockmgr

100021 3 udp 4045 nlockmgr

100021 4 udp 4045 nlockmgr

100021 1 tcp 4045 nlockmgr

100021 2 tcp 4045 nlockmgr

100021 3 tcp 4045 nlockmgr

100021 4 tcp 4045 nlockmgr

100024 1 udp 46339 status

100024 1 tcp 53947 status

100133 1 udp 46339

100133 1 tcp 53947

100011 1 udp 43899 rquotad

100005 1 udp 39977 mountd

100005 1 tcp 61756 mountd

100005 2 udp 39977 mountd

100005 2 tcp 61756 mountd

100005 3 udp 39977 mountd

100005 3 tcp 61756 mountd

100003 2 udp 2049 nfs

100003 3 udp 2049 nfs

100227 2 udp 2049

100227 3 udp 2049

100003 2 tcp 2049 nfs

100003 3 tcp 2049 nfs

100003 4 tcp 2049 nfs

100227 2 tcp 2049

100227 3 tcp 2049


111 udp and 2049 udp and tcp appear to be open, and portmapper is running. There don't appear to be any red flags I'm catching even when looking at it from the OS X client end.


I feel horrible asking this question here, but I see two things when searching for NFS in the OS X client forum:

1.) Good intentioned people pointing this way for answers and

2.) Others asking when the next Need For Speed game will be released for OS X


Any help/insight anyone could provide would be greatly appreciated.


Thanks,
Ryan


Message was edited by: rjanuary Removed formatting that didn't appear as expected.

iMac, Mac OS X (10.7.2)

Posted on Jan 3, 2012 11:26 PM

Reply
7 replies

Jan 7, 2012 8:01 AM in response to Mike Mackovitch

The only item between the clients and server at the present time is a gigabit switch.


Are there any particular NFS options that OS X clients would require? I've recently seen mention that the server needs to support both privileged and unprivileged ports. I'm working to verify that on the Solaris server at the present moment.


One other thing I will mention is that after installing the 10.7.2 update and a reboot I can perform the mount, and get a directory listing, but copying a file is almost out of the question. I've tried the mount with each version of NFS, showing no behavioral differences between them.

Mar 12, 2012 1:55 PM in response to rjanuary

Just wanted to report back that I just found a way to successfuly mount & use my NFS share!!!


Check out the following article:

http://www.techrepublic.com/blog/mac/mounting-nfs-volumes-in-os-x/430


I followed this article, used Disk Utility to define/mount the NFS share with the following options:

nfsv3,nolockd,sec=sys,noresvport


And for the local path I used /Network/share_name so that it will show up in the finder under:

Devices -> Name of my MacBook Pro -> Network


Please let me know if this works for you as well?

Jan 4, 2013 8:40 AM in response to JohanDC

Very tanks! I mount NFS shares from a Seagate BlackArmor NAS and after passing these parameters the Finder stopped showing interrupted server connections error! On Mac OS 10.8.2 dont have more NFS Mount menu on Disk Utility ... but I use terminal command line: sudo mount -t nfs -o sec=sys,nolock,noresvport,inet,soft,intr,timeo=900,retrans=3,proto=tcp [SERVER]:/DataVolume/[SHARE] /Volumes/[LOCAL_MOUNT]


Now I will look for folder owner problem on mounted folders. Tanks again!

NFS issues with finder

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.