Dear, folks.
A problem around the NFS/AFS translator as following occures in our
site:
AFS client running the translator: Sun (sun4m) with SunOS 4.1.3 rev.A
NFS client: Intel Paragon (486 hyper massive) with OSF/1 rel.1.1
The problem is a time lag for a file to be updated between the Sun
workstation and Paragon.
For example:
a) Make an executable file on the Sun with the cross-compiler, but on
the Paragon, the file does not seem to be the new one on the exact
time. After we have made access to the file in several times, It
surprises us with being updated, suddnely.
b) Run a program on Paragon and get a file as output, but we examine
it on the Sun, it seems not to be the latest one in a while.
We have tryed to throw out the old data on the cache with "fs flush"
or "fs flushvol" on the Sun, but it does not seems to be so effective.
So, these are the questions:
1) What is the problem?
2) How can we solve it?
Please tell us the answer or something.
Thanks in advance.
--
Susumu Miki ([EMAIL PROTECTED])
Tsukuba Research Center, Real World Computing Partnership, JAPAN
- Re: the NFS/AFS translator caching problem Susumu Miki
- Re: the NFS/AFS translator caching problem Susumu Miki
- Re: the NFS/AFS translator caching problem Susumu Miki
