[OpenAFS] Client synchronization issues/Client caches are not being updated

Ken Elkabany Ken@Elkabany.com
Tue, 2 Mar 2010 02:01:22 -0800


--005045015ea7b2fbae0480ce72c5
Content-Type: text/plain; charset=ISO-8859-1

I have six client machines all accessing a single openafs server. The server
and five clients are running Ubuntu 9.10 with openafs 1.4.10. About 80% of
the time when a client modifies files on the afs, the changes are not
reflected on the other clients, even after the file has been closed (a zip
file is unpacked in a directory, replacing all identically named files). If
a new file is copied, often times the other clients will not see it.
Sometimes, after a couple minutes, the files are appropriately updated.
Oddly enough, the sixth client, which is running Ubuntu 9.04 with openafs
1.4.9, always has the changes properly reflected on it. However, I cannot
guarantee that the openafs client version is the issue as the sixth client
is not running in the same conditions (not in a virtual machine), and is
also running external to the local area network of the other four clients.
Is this expected behavior? I don't recall this being a problem when all our
servers were on openafs 1.4.9. Is there a way to force the synchronization?

Thanks,

Ken

--005045015ea7b2fbae0480ce72c5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I have six client machines all accessing a single openafs server. The serve=
r and five clients are running Ubuntu 9.10 with openafs 1.4.10. About 80% o=
f the time when a client modifies files on the afs, the changes are not ref=
lected on the other clients, even after the file has been closed (a zip fil=
e is unpacked in a directory, replacing all identically named files). If a =
new file is copied, often times the other clients will not see it. Sometime=
s, after a couple minutes, the files are appropriately updated. Oddly enoug=
h, the sixth client, which is running Ubuntu 9.04 with openafs 1.4.9, alway=
s has the changes properly reflected on it. However, I cannot guarantee tha=
t the openafs client version is the issue as the sixth client is not runnin=
g in the same conditions (not in a virtual machine), and is also running ex=
ternal to the local area network of the other four clients. Is this expecte=
d behavior? I don't recall this being a problem when all our servers we=
re on openafs 1.4.9. Is there a way to force the synchronization?<div>
<br></div><div>Thanks,</div><div><br></div><div>Ken</div>

--005045015ea7b2fbae0480ce72c5--