Hello again,
Still no luck with getting a Tru64 5.1 client to 'vi' a NFS'ed share from
another 5.1 server.
These tests are done by modifying (using vi) a text file that's about 15
bytes in size.
With a NFS Server 5.1 ECO#5:
*) 5.1 ECO#5 client, vi fails, ctrl-c will interrupt
*) 5.1 ECO#0 client, vi fails, ctrl-c will interrupt
*) 4.0F ECO#4 client, vi succeeds!
NFS Server 4.0F ECO#4:
*) Client 5.1 ECO#5 vi succeeds (although, another 5.1 client failed and
locked the process)
Other points of consideration:
* In all conditions, using 'ed' to modify instead of 'vi' works fine
* creating a new file using vi works. Locking only affects existing files
* netstat -i shows a 1 in 360,000 Out Packet error ratio
* no difference was seen using either TCP or UDP as the protocol
* name resolution is via a distributed hosts file
Me thinks it's time to log a support call if there are no other suggestions
from you good folk.
Damien.
-----Original Message-----
From: Malczewski, Damien
Sent: Wednesday, 2 October 2002 5:56 PM
To: 'tru64-unix-managers_at_ornl.gov'
Subject: NFS Locking Problem
Hello all,
I have one NFS server and 6 NFS clients. All are running Tru64 5.1 with
patch kit 5.
One system gets stuck when trying to access files over the NFS share and
/var/adm/messages comes up with "NFS3 server .... not responding still
trying". Doing basic cd and ls listings are fine, but vi fails. So this
must be a locking problem of some sort. By turning locking off the nfs
client, I can then vi the files but some other process is still making the
share report the "not responding" message.
Looking through the managers list I see that other people have had similar
problems as well. Unless my searching has let me down, no summaries have
been posted.
Help! :-)
Thanks,
Damien.
Damien Malczewski
SAP Administrator
Information Services
SunRice
(Ricegrowers' Co-operative Limited ABN 55 007 481 156, Yanco Avenue Leeton,
trading as SunRice)
Received on Tue Oct 08 2002 - 02:55:06 NZDT