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