Hi All I am having some trouble with nfs when wanting to manual mount a nfs share. I am using 9.1 pro. When i use the following command: mount pc:/share /mnt i get the following error ( i did rcportmap start ): nfs server reported tcp not available, falling back to udp. When i use nfsclient in yast2 it mounts 100%. Regards _____________________________________________________________________ For super low premiums ,click here http://www.dialdirect.co.za/quote
On Thursday 12 August 2004 10:44 pm, it clown wrote:
Hi All
I am having some trouble with nfs when wanting to manual mount a nfs share. I am using 9.1 pro. When i use the following command: mount pc:/share /mnt i get the following error ( i did rcportmap start ):
nfs server reported tcp not available, falling back to udp.
When i use nfsclient in yast2 it mounts 100%.
Here's what I use as root. mount (target IP address):(path to target) Rich
it clown writes:
I am having some trouble with nfs when wanting to manual mount a nfs share. I am using 9.1 pro. When i use the following command: mount pc:/share /mnt i get the following error ( i did rcportmap start ):
nfs server reported tcp not available, falling back to udp.
When i use nfsclient in yast2 it mounts 100%.
NFS can operate over either TCP or UDP. TCP provides better data reliability but has higher overhead. Some NFS servers only support UDP (SuSE 9.1 supports both). When you mount a remote NFS share on a 9.1 client machine, it tries TCP first, and if the server does not support NFS over TCP, it falls back to UDP, and you get that message. However the remote share should still successfully mount. To silence that message, just add "udp" as a mount option (either on the command line or in your /etc/fstab file). E.g., mount -t nfs -o udp pc:/share /mnt -Ti -- R 1 3 5 Ti Kan |_|_|_| http://www.amb.org/ti | | | Vorsprung durch Technik 2 4 6
On Friday 13 Aug 2004 07:17, Ti Kan wrote:
it clown writes:
I am having some trouble with nfs when wanting to manual mount a nfs share. I am using 9.1 pro. When i use the following command: mount pc:/share /mnt i get the following error ( i did rcportmap start ):
nfs server reported tcp not available, falling back to udp.
When i use nfsclient in yast2 it mounts 100%.
NFS can operate over either TCP or UDP. TCP provides better data reliability but has higher overhead. Some NFS servers only support UDP (SuSE 9.1 supports both).
When you mount a remote NFS share on a 9.1 client machine, it tries TCP first, and if the server does not support NFS over TCP, it falls back to UDP, and you get that message. However the remote share should still successfully mount.
To silence that message, just add "udp" as a mount option (either on the command line or in your /etc/fstab file). E.g.,
mount -t nfs -o udp pc:/share /mnt
-Ti -- R 1 3 5 Ti Kan |_|_|_| http://www.amb.org/ti | | | Vorsprung durch Technik 2 4 6
und das spitzen popsen bangen tanken -- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan PGN
it clown
I am having some trouble with nfs when wanting to manual mount a nfs share. I am using 9.1 pro. When i use the following command: mount pc:/share /mnt i get the following error ( i did rcportmap start ):
nfs server reported tcp not available, falling back to udp.
It's not an error message. NFS over UDP was used in the past. You can check that the server provides NFS over TCP via $ /usr/sbin/rpcinfo -p pc program vers proto port ... 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs ... In the example above, both UDP and TCP are supported by the nfs daemon.
When i use nfsclient in yast2 it mounts 100%.
IMHO it just doesn't list the message. "netstat | grep nfs" will show if there is an NFS over TCP connection. If both the NFS server and client run SUSE Linux 9.1 then you did something wrong since NFS over TCP is started by default in this case. -- A.M.
On Fri, 13 Aug 2004 07:44:20 +0200, you wrote:
Hi All
I am having some trouble with nfs when wanting to manual mount a nfs share. I am using 9.1 pro. When i use the following command: mount pc:/share /mnt i get the following error ( i did rcportmap start ):
nfs server reported tcp not available, falling back to udp.
When i use nfsclient in yast2 it mounts 100%.
Did you read the error message and the man page for mount? SuSE NFS supports tcp as well as udp, unlike most NFS implementations. The "error" you're getting isn't an error, it's an advisory. The mount succeeded but not via tcp, via udp. If you want the mount to be silent (as far as that advisory goes), specify tcp or udp in the mount command. That info, and much more, is available in the linux help system. Try 'man man'. Mike- -- If you're not confused, you're not trying hard enough. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
I have exactly the same problem mounting remote NFS exports on SuSE9.1 No matter if NFS falls back to udp these shares are not mounted correctly, the are just plain empty. I think NFS implementation in SUSE 9.1 is screwed. Another box which runs SUSE 8.1 on the same network doesn't have this problems at all. I'm still pulling my hair trying to fix this problem. Alex On Fri, 13 Aug 2004, Michael W Cocke wrote:
On Fri, 13 Aug 2004 07:44:20 +0200, you wrote:
Hi All
I am having some trouble with nfs when wanting to manual mount a nfs share. I am using 9.1 pro. When i use the following command: mount pc:/share /mnt i get the following error ( i did rcportmap start ):
nfs server reported tcp not available, falling back to udp.
When i use nfsclient in yast2 it mounts 100%.
Did you read the error message and the man page for mount? SuSE NFS supports tcp as well as udp, unlike most NFS implementations. The "error" you're getting isn't an error, it's an advisory. The mount succeeded but not via tcp, via udp. If you want the mount to be silent (as far as that advisory goes), specify tcp or udp in the mount command.
That info, and much more, is available in the linux help system. Try 'man man'.
Mike-
-- If you're not confused, you're not trying hard enough. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Alex Daniloff writes:
I have exactly the same problem mounting remote NFS exports on SuSE9.1 No matter if NFS falls back to udp these shares are not mounted correctly, the are just plain empty. I think NFS implementation in SUSE 9.1 is screwed. Another box which runs SUSE 8.1 on the same network doesn't have this problems at all. I'm still pulling my hair trying to fix this problem.
My megaserver (SuSE 9.1) exports NFS to many different hosts running different OSes (other Linux of various distros and versions, Solaris, HP-UX, UnixWare, IRIX, AIX,...) all working just great. -Ti
I'm not exporting NFS shares but trying to imort from other UNIX hosts. On Friday 13 August 2004 03:07 pm, Ti Kan wrote:
Alex Daniloff writes:
I have exactly the same problem mounting remote NFS exports on SuSE9.1 No matter if NFS falls back to udp these shares are not mounted correctly, the are just plain empty. I think NFS implementation in SUSE 9.1 is screwed. Another box which runs SUSE 8.1 on the same network doesn't have this problems at all. I'm still pulling my hair trying to fix this problem.
My megaserver (SuSE 9.1) exports NFS to many different hosts running different OSes (other Linux of various distros and versions, Solaris, HP-UX, UnixWare, IRIX, AIX,...) all working just great.
-Ti
Alex Daniloff writes:
On Friday 13 August 2004 03:07 pm, Ti Kan wrote:
Alex Daniloff writes:
I have exactly the same problem mounting remote NFS exports on SuSE9.1 No matter if NFS falls back to udp these shares are not mounted correctly, the are just plain empty. I think NFS implementation in SUSE 9.1 is screwed. Another box which runs SUSE 8.1 on the same network doesn't have this problems at all. I'm still pulling my hair trying to fix this problem.
My megaserver (SuSE 9.1) exports NFS to many different hosts running different OSes (other Linux of various distros and versions, Solaris, HP-UX, UnixWare, IRIX, AIX,...) all working just great.
I'm not exporting NFS shares but trying to imort from other UNIX hosts.
No problem doing that here either. With NFS servers that supports only udp, I just mount with the udp mount option on SuSE 9.1 and all is well. -Ti
participants (7)
-
Alex Daniloff -
Alexandr Malusek -
C. Richard Matson -
it clown -
Michael W Cocke -
peter Nikolic -
ti＠amb.org