Board index Solaris

NFS server not responding, still trying

NFS server not responding, still trying

Post by gal.. » Fri, 22 Oct 1999 04:00:00



It is common for us to experience very sluggish system performance and
hung processes when we get the "NFS server (sever_name) not responding,
still trying" message due to a mounted NFS system going down. (We are
primarily using mounted NFS filesytems to move data files, usually with
shell scripts.)

I'd like to hear possible ways to reduce the impact of this error. I'm
considering adding the bg option to my NFS mounts. How about increasing
the timeo value? How about implementing CacheFS or Automounting?
Suggestions?

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 
Top

1. "NFS Server volume manangement (/vol) not responding still trying.."

"NFS Server volume manangement (/vol) not responding still trying.."
Running Solaris 7 and receive this error when trying to read cdrom.
Nothing shows up in the directory in /cdrom.

_______________________________________________
Submitted via WebNewsReader of http://www.interbulletin.com

2. Realtime Linux Workshop

3. NFS server not responding, still trying

4. Walmart Linux box modem info?

5. kernel: nfs: server myserver not responding, still trying

6. Setting up lpd in Caldera 1.3, cannot print:

7. NFS server for volume management (/vol) not responding still trying

8. Elmed

9. NFS server not responding still trying

10. Problem: "NFS Server xxx.xxx.xxx.xxx not responding, still trying"

11. nfs: server not responding still trying - Linux stops

12. NIS: server not responding for domain "noname"; still trying.

13. ypbind[xxx]: NIS server not responding for domain "ie-mydomain-nis"; still trying


All times are UTC
Board index