> Hi
>
I am having a problem serving NFS disk from one box (Workstation 600A 5/500,
DUnix V4.0D) to 2 other 600au boxes (DUnix V4.0D).
The problem is intermittent.
For example, when I log on my account (home directory is on the NFS disk)
a) via remote telnet, access is OK but some time very slow
b) via workstation consol, absolutely not failed to pass the CDE login.
When I looked in the messages file I see a lot of errors like:
.......
Jul 10 15:59:30 prodigy vmunix: NFS3 server paragon not responding still
trying
Jul 10 16:01:18 prodigy vmunix: NFS3 server paragon ok
Jul 10 16:01:30 prodigy vmunix: NFS3 server paragon not responding still
trying
Jul 10 16:03:51 prodigy vmunix: NFS3 server paragon ok
Jul 10 16:04:10 prodigy vmunix: NFS3 server paragon not responding still
trying
Jul 10 16:04:53 prodigy vmunix: NFS3 server paragon ok
Jul 10 16:05:10 prodigy vmunix: NFS3 server paragon not responding still
trying
Jul 10 16:05:58 prodigy vmunix: NFS3 server paragon ok
Jul 10 16:06:10 prodigy vmunix: NFS3 server paragon not responding still
trying
Jul 10 16:06:24 prodigy vmunix: NFS3 server paragon ok
...........(where paragon is the NFS server)
I also used NIS on three boxes.
One 600au machine is ok (512 MB memory and 4D40T graphic card), but the
other is not.(1GB and 4D60T graphic card)
Below is the nfsstat output on the problematic 600au:
======================================================
# nfsstat -c
Client rpc:
tcp: calls badxids badverfs timeouts newcreds
0 0 0 0 0
creates connects badconns inputs avails interrupts
0 0 0 0 0 0
udp: calls badxids badverfs timeouts newcreds retrans
198 0 0 65 0 0
badcalls timers waits
65 0 0
Client nfs:
calls retrans badcalls nclget nclsleep
133 45 0 133 0
Client nfs V2:
null getattr setattr root lookup readlink read
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
wrcache write create remove rename link symlink
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
mkdir rmdir readdir statfs
0 0% 0 0% 0 0% 0 0%
Client nfs V3:
null getattr setattr lookup access readlink read
0 0% 17 12% 5 3% 67 50% 15 11% 0 0% 5 3%
write create mkdir symlink mknod remove rmdir
8 6% 3 2% 0 0% 0 0% 0 0% 5 3% 0 0%
rename link readdir readdir+ fsstat fsinfo pathconf
2 1% 2 1% 0 0% 1 0% 2 1% 1 0% 0 0%
commit
0 0%
============================================================
I looked at the parameter configuration on both machines and they look the
same. The subsystem inet on both machines are the same.
I am not sure if NIS causes any problem, but the NIS configuration is also
similar. They both serve as Slave servers with the NFS server being the
master server.
I even reinstalled the Digital Unix OS and the same problem reappears.
I would appreciate if someone could problem some feedback or pointers.
Would there be any remote chances of the network hardware problem such that
it happens intermittentlly?
Thanks a log
Chung Ta
Syncrude Canada
Received on Sat Jul 11 1998 - 00:54:49 NZST