I have an Apple OS X 10.4.3 that was successfully connected to Suse Linux 9.2 NFS server. I upgraded to Suse 10.0 and now the Apple cannot find the Linux server. It can successfully ping the Linux IP address. What settings do I need when starting the Linux NFS services? There must be some differences between 9.2 and 10.0 that I'm missing. Thanks in advance, --Dan
On Sun, 2005-11-06 at 15:21 -0500, Dan Nash wrote:
I have an Apple OS X 10.4.3 that was successfully connected to Suse Linux 9.2 NFS server. I upgraded to Suse 10.0 and now the Apple cannot find the Linux server. It can successfully ping the Linux IP address. What settings do I need when starting the Linux NFS services? There must be some differences between 9.2 and 10.0 that I'm missing.
Probably the same thing I went through with OS-9 (Microware, not Apple) connectivity. The 2.6 kernel (where NFS now lives) uses a newer version of NFS by default. It also uses udp instead of tcp. Can you mount an export from OS/X on SUSE 10.0? When mounting on SUSE 10.0, I needed to add this to the fstab options: udp,nfsvers=2 I do not know how you specify this when exporting. Or even if you can. But maybe this will get you started in the right direction. Hope this helps. -- Roger Oberholtzer OPQ Systems AB
Hi, I'm also having a few problems with NFS on SuSE 10. I am trying to mount resources from a SLES 9 machine, presumably set up for nfsvers 3??? Each boot time, I get the error message that the "server reports TCP unavailable, resorting to UDP". I also occasionally see error messages to the effect of "server reports nfsvers 4 not available, switching to version 3". All in all, it means that each time I reboot my SuSE 10 machine, I have to log in as root and issue the command: mount -vat nfs, and more often than not this will pick up the nfs drives that aren't being mounted at boot time. FYI, here's the lines from /etc/fstab: 163.1.82.28:/home /home nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 163.1.82.28:/home1 /home1 nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 163.1.82.28:/home2 /home2 nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 What are the implications of using UDP and nfsvers=2 on security/performance etc.???? Anyone know what's going on? I have another AMD64 machine (SuSE 9.3), which has exactly the same problem. Best wishes, Jon. Roger Oberholtzer wrote:
On Sun, 2005-11-06 at 15:21 -0500, Dan Nash wrote:
I have an Apple OS X 10.4.3 that was successfully connected to Suse Linux 9.2 NFS server. I upgraded to Suse 10.0 and now the Apple cannot find the Linux server. It can successfully ping the Linux IP address. What settings do I need when starting the Linux NFS services? There must be some differences between 9.2 and 10.0 that I'm missing.
Probably the same thing I went through with OS-9 (Microware, not Apple) connectivity. The 2.6 kernel (where NFS now lives) uses a newer version of NFS by default. It also uses udp instead of tcp.
Can you mount an export from OS/X on SUSE 10.0?
When mounting on SUSE 10.0, I needed to add this to the fstab options:
udp,nfsvers=2
I do not know how you specify this when exporting. Or even if you can. But maybe this will get you started in the right direction.
Hope this helps.
-- Jonathan Brooks (Ph.D.) Research Assistant. PaIN Group, Department of Human Anatomy & Genetics, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: +44(0)1865-282654 fax: +44(0)1865-282656 web: http://www.fmrib.ox.ac.uk/~jon
In SUSE 10.0 they finally got the /net working right again. Why don't you turn on the atuofs, setup, auto.master, and auto.net. Then as a standard user say the machine is crab, you can then do a cd /net/crab/to-your_exported_directory. It requires no root command. If you turn on the timeout, if you are not using it, it will even unmount the file without any problem. Jonathan Brooks wrote:
Hi,
I'm also having a few problems with NFS on SuSE 10. I am trying to mount resources from a SLES 9 machine, presumably set up for nfsvers 3???
Each boot time, I get the error message that the "server reports TCP unavailable, resorting to UDP". I also occasionally see error messages to the effect of "server reports nfsvers 4 not available, switching to version 3".
All in all, it means that each time I reboot my SuSE 10 machine, I have to log in as root and issue the command: mount -vat nfs, and more often than not this will pick up the nfs drives that aren't being mounted at boot time.
FYI, here's the lines from /etc/fstab:
163.1.82.28:/home /home nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 163.1.82.28:/home1 /home1 nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 163.1.82.28:/home2 /home2 nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0
What are the implications of using UDP and nfsvers=2 on security/performance etc.????
Anyone know what's going on? I have another AMD64 machine (SuSE 9.3), which has exactly the same problem.
Best wishes,
Jon.
Roger Oberholtzer wrote:
On Sun, 2005-11-06 at 15:21 -0500, Dan Nash wrote:
I have an Apple OS X 10.4.3 that was successfully connected to Suse Linux 9.2 NFS server. I upgraded to Suse 10.0 and now the Apple cannot find the Linux server. It can successfully ping the Linux IP address. What settings do I need when starting the Linux NFS services? There must be some differences between 9.2 and 10.0 that I'm missing.
Probably the same thing I went through with OS-9 (Microware, not Apple) connectivity. The 2.6 kernel (where NFS now lives) uses a newer version of NFS by default. It also uses udp instead of tcp.
Can you mount an export from OS/X on SUSE 10.0?
When mounting on SUSE 10.0, I needed to add this to the fstab options:
udp,nfsvers=2
I do not know how you specify this when exporting. Or even if you can. But maybe this will get you started in the right direction.
Hope this helps.
-- Joseph Loo jloo@acm.org
On Mon, 2005-11-07 at 21:24 -0800, Joseph Loo wrote:
In SUSE 10.0 they finally got the /net working right again. Why don't you turn on the atuofs, setup, auto.master, and auto.net. Then as a standard user say the machine is crab, you can then do a cd /net/crab/to-your_exported_directory. It requires no root command. If you turn on the timeout, if you are not using it, it will even unmount the file without any problem.
Where is this all documented? -- Roger Oberholtzer OPQ Systems AB
Joseph Loo wrote:
In SUSE 10.0 they finally got the /net working right again. Why don't you turn on the atuofs, setup, auto.master, and auto.net. Then as a standard user say the machine is crab, you can then do a cd /net/crab/to-your_exported_directory. It requires no root command. If you turn on the timeout, if you are not using it, it will even unmount the file without any problem.
Jonathan Brooks wrote:
Hi,
I'm also having a few problems with NFS on SuSE 10. I am trying to mount resources from a SLES 9 machine, presumably set up for nfsvers 3???
Each boot time, I get the error message that the "server reports TCP unavailable, resorting to UDP". I also occasionally see error messages to the effect of "server reports nfsvers 4 not available, switching to version 3".
All in all, it means that each time I reboot my SuSE 10 machine, I have to log in as root and issue the command: mount -vat nfs, and more often than not this will pick up the nfs drives that aren't being mounted at boot time.
FYI, here's the lines from /etc/fstab:
163.1.82.28:/home /home nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 163.1.82.28:/home1 /home1 nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 163.1.82.28:/home2 /home2 nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0
What are the implications of using UDP and nfsvers=2 on security/performance etc.????
Anyone know what's going on? I have another AMD64 machine (SuSE 9.3), which has exactly the same problem.
Best wishes,
Jon.
Roger Oberholtzer wrote:
On Sun, 2005-11-06 at 15:21 -0500, Dan Nash wrote:
I have an Apple OS X 10.4.3 that was successfully connected to Suse Linux 9.2 NFS server. I upgraded to Suse 10.0 and now the Apple cannot find the Linux server. It can successfully ping the Linux IP address. What settings do I need when starting the Linux NFS services? There must be some differences between 9.2 and 10.0 that I'm missing.
Probably the same thing I went through with OS-9 (Microware, not Apple) connectivity. The 2.6 kernel (where NFS now lives) uses a newer version of NFS by default. It also uses udp instead of tcp.
Can you mount an export from OS/X on SUSE 10.0?
When mounting on SUSE 10.0, I needed to add this to the fstab options:
udp,nfsvers=2
I do not know how you specify this when exporting. Or even if you can. But maybe this will get you started in the right direction.
Hope this helps.
Hi Joseph, Thanks for the info, but rather than using automounting, I would like to be able to use NFS options in /etc/fstab. I would dearly like to know why our AMD64 machines have so much trouble connecting to our SLES server to mount NFS drives at boot time. Automounting is a great system, but I don't need it here. There are only a few machines to administer, and fstab is just easier. Best wishes, Jon. -- Jonathan Brooks (Ph.D.) Research Assistant. PaIN Group, Department of Human Anatomy & Genetics, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: +44(0)1865-282654 fax: +44(0)1865-282656 web: http://www.fmrib.ox.ac.uk/~jon
There is an option on the /etc/fstab that does the mounting automtaically. It has to do with the last 2 numbers on the list. I suggest you add 1 n where n is the order of mounting. If you have 0 in the first number, it will not automatically moun the partition. By the way I love useing automount.. I use it only on a few machines. at home. To me it just offers a lot of flexibility with a small performance penalty. Also the /net feature allows me to easily access other machins exported file system without using root. Jonathan Brooks wrote:
Joseph Loo wrote:
In SUSE 10.0 they finally got the /net working right again. Why don't you turn on the atuofs, setup, auto.master, and auto.net. Then as a standard user say the machine is crab, you can then do a cd /net/crab/to-your_exported_directory. It requires no root command. If you turn on the timeout, if you are not using it, it will even unmount the file without any problem.
Jonathan Brooks wrote:
Hi,
I'm also having a few problems with NFS on SuSE 10. I am trying to mount resources from a SLES 9 machine, presumably set up for nfsvers 3???
Each boot time, I get the error message that the "server reports TCP unavailable, resorting to UDP". I also occasionally see error messages to the effect of "server reports nfsvers 4 not available, switching to version 3".
All in all, it means that each time I reboot my SuSE 10 machine, I have to log in as root and issue the command: mount -vat nfs, and more often than not this will pick up the nfs drives that aren't being mounted at boot time.
FYI, here's the lines from /etc/fstab:
163.1.82.28:/home /home nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 163.1.82.28:/home1 /home1 nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0 163.1.82.28:/home2 /home2 nfs rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0
What are the implications of using UDP and nfsvers=2 on security/performance etc.????
Anyone know what's going on? I have another AMD64 machine (SuSE 9.3), which has exactly the same problem.
Best wishes,
Jon.
Roger Oberholtzer wrote:
On Sun, 2005-11-06 at 15:21 -0500, Dan Nash wrote:
I have an Apple OS X 10.4.3 that was successfully connected to Suse Linux 9.2 NFS server. I upgraded to Suse 10.0 and now the Apple cannot find the Linux server. It can successfully ping the Linux IP address. What settings do I need when starting the Linux NFS services? There must be some differences between 9.2 and 10.0 that I'm missing.
Probably the same thing I went through with OS-9 (Microware, not Apple) connectivity. The 2.6 kernel (where NFS now lives) uses a newer version of NFS by default. It also uses udp instead of tcp.
Can you mount an export from OS/X on SUSE 10.0?
When mounting on SUSE 10.0, I needed to add this to the fstab options:
udp,nfsvers=2
I do not know how you specify this when exporting. Or even if you can. But maybe this will get you started in the right direction.
Hope this helps.
Hi Joseph,
Thanks for the info, but rather than using automounting, I would like to be able to use NFS options in /etc/fstab. I would dearly like to know why our AMD64 machines have so much trouble connecting to our SLES server to mount NFS drives at boot time.
Automounting is a great system, but I don't need it here. There are only a few machines to administer, and fstab is just easier.
Best wishes,
Jon.
-- Joseph Loo jloo@acm.org
On Tue, 2005-11-08 at 18:55 -0800, Joseph Loo wrote:
There is an option on the /etc/fstab that does the mounting automtaically. It has to do with the last 2 numbers on the list. I suggest you add 1 n where n is the order of mounting. If you have 0 in the first number, it will not automatically moun the partition.
Naahh.. The fifth number on the line (I get this from the fstab man page) is related to the dump() command, and the sixth (last number on the line) is related to fsck(). I think you are thinking of the key word 'auto' or 'noauto' that you can provide in the comma separated list of mount options in item four on the line. To understand those, look at the 'mount' man page. Still, this is only automatic relative to when the system boots. It does not mean that they will be automatically mounted on demand at a later time. 'autofs' seems to be for that. -- Roger Oberholtzer OPQ Systems AB
On Mon, 7 Nov 2005 07:21 am, Dan Nash wrote:
I have an Apple OS X 10.4.3 that was successfully connected to Suse Linux 9.2 NFS server. I upgraded to Suse 10.0 and now the Apple cannot find the Linux server. It can successfully ping the Linux IP address. What settings do I need when starting the Linux NFS services? There must be some differences between 9.2 and 10.0 that I'm missing.
One thing that helped (in 9.x as well) was to put the "insecure" option on the share in /etc/exports. Apple explain how not having "insecure" doesn't actually make you any more secure, and I rather agree with them. If you get complaints about "Service not registered" then you need to start portmap. If putting a tail on /var/log/messages doesn't reveal any activity, then it's probably firewall settings. my $.02 michaelj -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166 No matter how much you pay for software, you always get less than you hoped. Unless you pay nothing, then you get more.
participants (5)
-
Dan Nash -
Jonathan Brooks -
Joseph Loo -
Michael James -
Roger Oberholtzer