Can't mount nfs volume - time out

Question

How can i find coordinate of point "C", when i know only:

1) Distance from "A" to "B";

2) Angle

3) Start point

In JS that look's like:

let A = {x: 50, y: 30},
    B = {x: 50, y: 80},
    C = {x: null, y: null};
let angle = 345;

let distanceBetweenAB = (B.x - A.x) + (B.y - A.y);

C = ?

Detailed in the picture:

Solution 1

So, NFS is weird in the it relys on portmapper to be running, so it can map a specific port to an RPC port. (I guess it's not weird. It's just the way it works.) If NFS is up before portmapper, NFS doesn't know how to route requests, because it checks portmapper for this at the start of the process. If portmapper is not up before NFS, NFS doesn't know how to map port to rpc.

Here's more documentation about the process (even though its for CentOS, it's still relevant): http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s2-nfs-methodology-portmap.html

As for your new error message, reboot the box you're mounting with and remount to see if the error comes back.

Solution 2

to summarize the solution from given answers, following steps below directed me to the right direction to fixing NFS mount issue without restating the box.

1. run a tcpdump in client side to the NFS server IP address (assuming it's 1.2.3.4)

   tcpdump -i <replace-with-correct-INTERFACE_name -n host 1.2.3.4
   

2. keep running tcpdump and try mounting the NFS share path.

3. lookup for the ports NFS is communicating with the server to mounting the path (in your case [tcpdump result in edit revision], shows those are ports: 880, 2049 only).

4. do telnet on NFS server IP and all the ports you got from tcpdump output in step3 and make sure you have telnet and ports are open from server side to client (for your case, only below two ports found).

   telnet 1.2.3.4 880
   telnet 1.2.3.4 2049
   

5. if you don't have telnet on any of those ports captured in step3, you need to open those ports at netwrok level (server side and/or firewall if you have)

6. try to mount the NFS again now.

Solution 3

tcpdump -i $LAN_IF -n host 10.10.10.2

should show you which of the NFS components fails.

Solution 4

Well i used to get the same error. I realized the only reason for there to be a timeout is because the connection has not been established properly. Digging deeper into the problem, I checked my firewall, and damnn NFS4 service was blocked !!

Solutiion:- Use the below command to configure your firewall settings and add * next to NFS4 service to enable it.

$ sudo system-config-firewall-tui

View more solutions

Comments

[CIA]

Is selinux enabled/disabled?

[Nathan]

@CIA to the best of my knowledge, selinux is neither installed nor supported on OpenSUSE.

[CIA]

Are you sure? As of version 11.1, openSUSE contains SELinux “basic enablement”. news.opensuse.org/2008/08/20/…

[Nathan]

The fileserver is running OpenSuSE 11.0

[CIA]

I can see you are able to ping to your nfs box. Are you able to ping your server from the nfs box? Also, were you trying to mount to ~/root/raid or did you mean to mount to /raid? And for your /etc/exports, have you tried explicitly defining the IP instead of using "*"?

[Nathan]

1: Yes. 2: ~/raid is a symlink to /mnt/raid. Specifying the full path doesn't change the behavior. This is how I have always mounted the export. 3: * should be more permissive than explicitly defining the IP, and it's how the server has always been configured. DHCP clients sometimes access this export, so explicit IP assignment won't work in the long term.

[CIA]

You have multiple systems connecting to this nfs? Are any of them having problems mounting as well?

[Bob__]

What do you mean with a = 345*?

[High Performance Mark]

I'm voting to close this question as off-topic because it is not about programming.

[Gleb]

@Bob__ 345* - it is degrees

[Bob__]

In your drawing, a seems to be the measure of an inner angle of a triangle. 345 degrees seems a bit too much. It's the heading of AC relative to some coordinate system, a random value or a typo for 34.5?

[Gleb]

@High Performance Mark sorry, that common question in various programming languages. Now i write it in javascript.

[Nathan]

I can connect to 111 and 2049. I think the other ports may be randomly assigned, since they're different on my server (check my edit to the post above).

[Nathan]

I have added tcpdump information to the question. Let me know if you find it helpful.

[Hauke Laging]

I don't understand the entries like 10.10.10.10.316725468. But it's obvious that you use NFS4 and that communication with the server is possible in general. I didn't know that tcpdump understands NFS. I just read that you get more NFS related information by giving -vv as an argument. It seems that your client calls the NFS "command" "176 getattr fh 0,0/35" and shortly after that finishes the connection. Even more strange: The server continues sending data after that and gets a connection reset. There's no need to print lines after the first "Flags [R.]".

[Nathan]

I don't think I'm actually using NFSv4. I believe I have it set up with v3. Could this be the source of the problem?

[Hauke Laging]

OK, I am not familiar enough with NFS. TCP on port 2049 was possible with NFSv3. I thought that nonetheless connections to portmapper and mountd were necessary (which are not necessary in NFSv4).

[Nathan]

I think I've seen the "new" error message before, and it doesn't appear to actually matter when it comes to being able to mount the export. It's quite possibly related to the ancient version of OpenSUSE we're running. One day maybe I'll get an intern to upgrade it :). Anyway, thanks for the help.

[Gleb]

Thank's, how to find distance between BC, i don't now: distanceBC = tan(angle) ?

[Gleb]

Thank. Direction from A to B, that can be write like: distanceBetweenAB = (B.x - A.x) + (B.y - A.y) ?

[Nico Schertler]

It is supposed to be a vector: dir = (B.x - A.x, B.y - A.y).

[pgoetz]

For NFSv4 you only need port 2049. rpcbind runs on port 111 and isn't needed by NFSv4. In fact, because rpcbind can be used to amplify DDOS attacks, having an open 111 port could get you quarantined by your information security office.