We've been seeing alot of 'NFS3 server servername not responding still trying' followed by 'NFS3 server servername ok' messages. Alot of them.
It's relaly only on our DEC hardware running Digital UNIX 4.0d.
Has anyone seen this before and found a fix? It's starting to affect our performance, especially trying to put some database files on them.
It's happening on multiple DEC boxes, against multiple filers (3 F760).
-- -------------------------------------------------------------------------- Cliff Nadler Collective Technologies, Inc. (a Pencom Company) cnadler@colltech.com (617)-443-1144 -------------------------------------------------------------------------- To win, you must treat a pressure situation as an opportunity to succeed, not an opportunity to fail Gardner Dickinson
Vaguely remember seeing similar messages on our DS20 @ 4.0F It turned out to be a LAN speed mismatch between the system and the switch. Remember that the speed must be set at the ">>>" boot prompt also. Here is my notes from that call: disable autonegotiate on the switch and set the port to 100 full. shut the DS20 and at the '>>>' prompt do:
set ewa0_mode fastfd init boot
[P.S. your lan interface logical name may not be ewa0]
-- Begin original message --
From: Cliff Nadler cnadler@colltech.com Date: Mon, 22 May 2000 14:06:42 -0500 (CDT) Subject: NFS problems between Tru64 UNIX and F760's (5.3.5) To: toasters@mathworks.com
We've been seeing alot of 'NFS3 server servername not responding still trying' followed by 'NFS3 server servername ok' messages. Alot of them.
It's relaly only on our DEC hardware running Digital UNIX 4.0d.
Has anyone seen this before and found a fix? It's starting to affect our performance, especially trying to put some database files on them.
It's happening on multiple DEC boxes, against multiple filers (3 F760).
--
Cliff Nadler Collective Technologies, Inc. (a Pencom Company) cnadler@colltech.com (617)-443-1144
To win, you must treat a pressure situation as an opportunity to succeed, not an opportunity to fail Gardner Dickinson
-- End original message --
---philip thomas
Our occurrences have decreased quite a bit, but persist, so sumarize to the list, please. We had this problem researched and found that DEC had the UBC able to use 100 % of RAM and the list of free pages was so long that it never finished checking the list before it got many more requests to check the list. The were also some patches added called performance patch set. I think they were in patch kit #5 even though they were announced as being in patch kit #3. We learned that "NFS server $server not responding" means that Tru64UNIX was clogging its own data and had nothing to do with any NFS server.
At 2:06 PM -0500 5/22/00, Cliff Nadler wrote:
We've been seeing alot of 'NFS3 server servername not responding still trying' followed by 'NFS3 server servername ok' messages. Alot of them.
It's relaly only on our DEC hardware running Digital UNIX 4.0d.
Has anyone seen this before and found a fix? It's starting to affect our performance, especially trying to put some database files on them.
It's happening on multiple DEC boxes, against multiple filers (3 F760).
--
Cliff Nadler Collective Technologies, Inc. (a Pencom Company) cnadler@colltech.com (617)-443-1144
To win, you must treat a pressure situation as an opportunity to succeed, not an opportunity to fail Gardner Dickinson
}}}===============>> LLNL James E. Harm (Jim); jharm@llnl.gov (925) 422-4018 Page: 423-7705x57152
-
Cliff Nadler -
Jim Harm -
Philip Thomas