Hello listmates,
Yes, I know - Macs and NFS do not co-exist easily. Still I've got to make this happen somehow.
In short - we have two CentOS-based NFS servers. They work fine with a variety of Linux machines but when I try to mount them from a Mac OS X 10.5 or 10.6 machine I get nowhere. I.e., the Mac does not complain yet reads nothing over the NFS.
Has anybody seen this? Does anybody know of a fix?
Thanks.
Boris.
On Wed, 29 Jun 2011, Boris Epstein wrote:
In short - we have two CentOS-based NFS servers. They work fine with a variety of Linux machines but when I try to mount them from a Mac OS X 10.5 or 10.6 machine I get nowhere. I.e., the Mac does not complain yet reads nothing over the NFS.
I have CentOS 5.5 NFS servers and a load of Macs, both Leopard and Snow Leopard. I too had a lot of NFS trouble, especially for multi-homed NFS servers, until I switched from NFS over udp to NFS over tcp (for the Macs only), and now everything works well. I even had trouble with NFS over udp to Mac clients from an OSX NFS server.
Steve
On Wed, Jun 29, 2011 at 5:27 PM, Steve Thompson smt@vgersoft.com wrote:
On Wed, 29 Jun 2011, Boris Epstein wrote:
In short - we have two CentOS-based NFS servers. They work fine with a variety of Linux machines but when I try to mount them from a Mac OS X 10.5 or 10.6 machine I get nowhere. I.e., the Mac does not complain yet reads nothing over the NFS.
I have CentOS 5.5 NFS servers and a load of Macs, both Leopard and Snow Leopard. I too had a lot of NFS trouble, especially for multi-homed NFS servers, until I switched from NFS over udp to NFS over tcp (for the Macs only), and now everything works well. I even had trouble with NFS over udp to Mac clients from an OSX NFS server.
Steve _______________________________________________
Steve,
Thanks. I am only doing NFS over TCP and still no dice. Any special options you use either on the client or on the server side?
Boris.
On Wed, 29 Jun 2011, Boris Epstein wrote:
Thanks. I am only doing NFS over TCP and still no dice. Any special options you use either on the client or on the server side?
As Tom mentioned, you need the "insecure" exports option on the NFS server side, otherwise I don't do anything special on the client. I'm sourcing the automount maps through LDAP. Try mounting via IP address rather than NFS server name; I've had some issues with this on Mac clients.
Steve
As Tom mentioned, you need the "insecure" exports option on the NFS server side, otherwise I don't do anything special on the client. I'm sourcing the automount maps through LDAP. Try mounting via IP address rather than NFS server name; I've had some issues with this on Mac clients.
Steve _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I wish this could help but I am exporting with "insecure" already...
Boris.
On Thu, Jun 30, 2011 at 10:20 AM, Boris Epstein borepstein@gmail.com wrote:
As Tom mentioned, you need the "insecure" exports option on the NFS server side, otherwise I don't do anything special on the client. I'm sourcing the automount maps through LDAP. Try mounting via IP address rather than NFS server name; I've had some issues with this on Mac clients.
I wish this could help but I am exporting with "insecure" already...
Is the OS X firewall blocking nfs?
How are you mounting the export? If you're not trying it from within Terminal, does it work from within it?
Is the OS X firewall blocking nfs?
How are you mounting the export? If you're not trying it from within Terminal, does it work from within it? ______________________________________________
The OS X firewall dos not appear to be a factor. Actually it works just fine when I turn off the firewall on the CentOS end.
Could it be that even when I am trying to mount over the TCP the NFS client on the Mac OS X side still tried to connect to some UDP port? I am asking that because everyone else mounts just fine with the firewall up on the server end.
Boris.
Boris Epstein wrote:
Is the OS X firewall blocking nfs?
How are you mounting the export? If you're not trying it from within Terminal, does it work from within it? ______________________________________________
The OS X firewall dos not appear to be a factor. Actually it works just fine when I turn off the firewall on the CentOS end.
Could it be that even when I am trying to mount over the TCP the NFS client on the Mac OS X side still tried to connect to some UDP port? I am asking that because everyone else mounts just fine with the firewall up on the server end.
As I recall OS X only does NFS via TCP - other clients can use UDP - make sure your CentOS firewall has the TCP ports open. HTH
Boris. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Tue, Jul 5, 2011 at 1:11 PM, Rob Kampen rkampen@kampensonline.com wrote:
Boris Epstein wrote:
Is the OS X firewall blocking nfs?
How are you mounting the export? If you're not trying it from within Terminal, does it work from within it?
The OS X firewall dos not appear to be a factor. Actually it works just fine when I turn off the firewall on the CentOS end.
Could it be that even when I am trying to mount over the TCP the NFS client on the Mac OS X side still tried to connect to some UDP port? I am asking that because everyone else mounts just fine with the firewall up on the server end.
As I recall OS X only does NFS via TCP - other clients can use UDP - make sure your CentOS firewall has the TCP ports open.
OS X does use TCP but I've just run tcpdump on an F15 VM while mounting and unmounting an NFS share from my Mac. Both the mount and umount result in four UDP packets, two to the portmapper and two to random ports.
I don't have time to experiment further right now but perhaps opening up 111 UDP will allow your Macs to mount the NFS shares.
On Tue, 2011-07-05 at 22:13 -0400, Tom H wrote:
On Tue, Jul 5, 2011 at 1:11 PM, Rob Kampen rkampen@kampensonline.com wrote:
Boris Epstein wrote:
Is the OS X firewall blocking nfs?
How are you mounting the export? If you're not trying it from within Terminal, does it work from within it?
The OS X firewall dos not appear to be a factor. Actually it works just fine when I turn off the firewall on the CentOS end.
Could it be that even when I am trying to mount over the TCP the NFS client on the Mac OS X side still tried to connect to some UDP port? I am asking that because everyone else mounts just fine with the firewall up on the server end.
As I recall OS X only does NFS via TCP - other clients can use UDP - make sure your CentOS firewall has the TCP ports open.
OS X does use TCP but I've just run tcpdump on an F15 VM while mounting and unmounting an NFS share from my Mac. Both the mount and umount result in four UDP packets, two to the portmapper and two to random ports.
I don't have time to experiment further right now but perhaps opening up 111 UDP will allow your Macs to mount the NFS shares.
NFSv3 uses the nfs port (TCP or UDP), portmapper (UDP) and some random UDP ports for quota, lockd, mount, and statd. These random ports can be fixed by setting them in /etc/sysconfig/nfs. They are normally commented out, but uncommenting them (and setting them to different values if so required) will fix them so you can firewall them.
Louis
On Wed, Jul 6, 2011 at 6:54 AM, Louis Lagendijk louis@lagendijk.xs4all.nl wrote:
On Tue, 2011-07-05 at 22:13 -0400, Tom H wrote:
On Tue, Jul 5, 2011 at 1:11 PM, Rob Kampen rkampen@kampensonline.com wrote:
Boris Epstein wrote:
Is the OS X firewall blocking nfs?
How are you mounting the export? If you're not trying it from within Terminal, does it work from within it?
The OS X firewall dos not appear to be a factor. Actually it works just fine when I turn off the firewall on the CentOS end.
Could it be that even when I am trying to mount over the TCP the NFS client on the Mac OS X side still tried to connect to some UDP port? I am asking that because everyone else mounts just fine with the firewall up on the server end.
As I recall OS X only does NFS via TCP - other clients can use UDP - make sure your CentOS firewall has the TCP ports open.
OS X does use TCP but I've just run tcpdump on an F15 VM while mounting and unmounting an NFS share from my Mac. Both the mount and umount result in four UDP packets, two to the portmapper and two to random ports.
I don't have time to experiment further right now but perhaps opening up 111 UDP will allow your Macs to mount the NFS shares.
NFSv3 uses the nfs port (TCP or UDP), portmapper (UDP) and some random UDP ports for quota, lockd, mount, and statd. These random ports can be fixed by setting them in /etc/sysconfig/nfs. They are normally commented out, but uncommenting them (and setting them to different values if so required) will fix them so you can firewall them.
Thanks doe the reminder! :)
My mind's been corrupted by recent Linux releases; I assumed that OS X defaulted to nfsv4 and tcp and my mind didn't connect the random ports with the pre-nfsv4 nfs elements (probably also because I always make them static!).
It does default to tcp but doesn't default to nfsv4.
Specifying "-o tcp" produces the udp packets as not specifying "-o tcp" so OS X's trying tcp and then falls back to udp.
Specifying "-o vers=4.0alpha" produces no udp packets. Perhaps the version of OS X being released this summer'll have a non-alpha nfsv4 mount_nfs...
On Tue, 5 Jul 2011, Boris Epstein wrote:
To: CentOS mailing list centos@centos.org From: Boris Epstein borepstein@gmail.com Subject: Re: [CentOS] mounting a CentOS 5.5-based NFS partitions from a Mac OS X machine
Is the OS X firewall blocking nfs?
How are you mounting the export? If you're not trying it from within Terminal, does it work from within it? ______________________________________________
The OS X firewall dos not appear to be a factor. Actually it works just fine when I turn off the firewall on the CentOS end.
Could it be that even when I am trying to mount over the TCP the NFS client on the Mac OS X side still tried to connect to some UDP port? I am asking that because everyone else mounts just fine with the firewall up on the server end.
Hi Boris. For any network connectivity problems, I'd recommend using wireshark. It's in the Centos updates repo. Just try 'yum info wireshark*' Running that will enable you pinpoint what your network problem is.
Kind Regards,
Keith Roberts
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
On Wed, Jun 29, 2011 at 05:30:02PM -0400, Boris Epstein wrote:
Thanks. I am only doing NFS over TCP and still no dice. Any special options you use either on the client or on the server side?
Two things to be aware of on a Mac 1) default mounts are from a non-privileged port. So your exports on CentOS needs to have 'insecure' as an option eg /directory mac_client(no_root_squash,async,insecure)
2) The MacOS X automounter doesn't play nice with all GUI applications. eg I had my mp3 collection exported and automounted on the Mac; iTunes played it fine. Until I left it idle and the filesystem unmounted. Then when I told iTunes to play it couldn't find the files. 'cos iTunes maintains a HFS+ path and it couldn't resolve the top of the path 'cos the file system was unmounted so it never caused the automounter to wake up.
So static mounts and "insecure" and it works.
For some values of; with 10.5 if I tried to use DVD Player to play VOB files then the Mac would reliably kernel crash after a few minutes. Heheheheh.
On Wed, Jun 29, 2011 at 5:14 PM, Boris Epstein borepstein@gmail.com wrote:
In short - we have two CentOS-based NFS servers. They work fine with a variety of Linux machines but when I try to mount them from a Mac OS X 10.5 or 10.6 machine I get nowhere. I.e., the Mac does not complain yet reads nothing over the NFS.
Has anybody seen this? Does anybody know of a fix?
You need "insecure" in the export options for OS X to allow you to mount an NFS volume.
-
Boris Epstein -
Keith Roberts -
Louis Lagendijk -
Rob Kampen -
Stephen Harris -
Steve Thompson -
Tom H