NFS3 RFS3_xxx, RPC: timed out

From: Dr. Otto Titze (titze@ikp.tu-darmstadt.de)
Date: Wed Oct 29 2003 - 06:20:07 EST


Hi,

users on a node A but with their home directory on node B
(both Tru64 V5.1B) get the message

NFS3 RFS3_xxx failed for server B, RPC: timed out
(xxx=read,getattr)

when the are using certain utilities like netscape, pine,
dtmail which access files on their home directory. After
some time the utility pops up but with limited information.

Besides that the network seems to behave normal
- ping works between A and B
- nfs mounted disks on A(from B) and on B(from A) are ok
   (no errors when accessing files with ls, cat...)

Looking through the archives in a similar case it was
suggested to autonegotiation problem on switches. Indeed the
error occurs after a total power black out yesterday with
the result that we had to replace the switch (A, B was on)
with another type of switch.

But changing the particular ports on the new switch to
manual settings did not help.

Therefore I have a few questions
1. What is the difference berween normal NFS behavior
    and NFS3 RFS3?
2. Could a particular software setting be improved
(For just to play around with the port speeds:)
3. How can I find out the actual NIC port speeds on A,B?
    (I unsuccessfully looked at hwmgr, ifconfig but
     ifconfig obviously only can set a new value?)

I appreciate any hints, what I could do further.

Thanks

Regards

Otto

-- 
  -------------------------------------------
| Dr. Otto Titze, Kernphysik TUD           |
| Schlossgartenstr. 9, D-64289 Darmstadt   |
| titze@ikp.tu-darmstadt.de                |
| Tel: +49(6151)16-2916,FAX:16-4321        |
  -------------------------------------------


This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:41 EDT