|
|
When the network or server has problems, programs that access hard mounted remote files will fail differently than those that access soft mounted remote files. Hard mounted remote resources cause the client's kernel to retry the requests until the server responds again. Soft mounted remote resources cause the client's system calls to return an error after trying for a while. mount is like any other program: if the server for a remote resource fails to respond, and the hard option has been used, the kernel retries the mount until it succeeds.
When a resource is hard mounted, a program that tries to access it hangs if the server fails to respond. In this case, NFS displays the message
NFS server hostname not responding, still tryingon the console. When the server finally responds, the message
NFS server hostname okappears on the console.
Any program accessing a soft mounted resource whose server is not responding may or may not check the return conditions. If it does, it prints an error message in the form
... hostname server not responding: RPC: Timed out
To clear server problems, do the following:
to see if the server is up. If it is up and running, it prints a list of program, version, protocol, and port numbers, similar to the following:
program version netid address service owner 100000 3 icmp 0.0.0.0.0.111 rpcbind superuser 100000 2 icmp 0.0.0.0.0.111 rpcbind superuser 100000 3 udp 0.0.0.0.0.111 rpcbind superuser 100000 2 udp 0.0.0.0.0.111 rpcbind superuser 100000 3 tcp 0.0.0.0.0.111 rpcbind superuser 100000 2 tcp 0.0.0.0.0.111 rpcbind superuser 100000 3 ticotsord hulk.rpc rpcbind superuser 100000 3 ticots hulk.rpc rpcbind superuser 100000 3 ticlts hulk.rpc rpcbind superuser . . . . . . . . . . . . . . . . . .