[OpenAFS] RO volumes disappearing?
Christopher Arnold
chris@pictage.com
Fri, 12 Dec 2003 09:46:25 -0800
This is a multi-part message in MIME format.
------=_NextPart_000_00FD_01C3C094.CF207710
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Recently I've noticed an odd problem in our environment and can't seem =
to
track down the source. We are running 1.2.10 servers/clients on redhat =
linux 7.3/8.0 in
two locations connected via a T3. We have 2 read-only sites created for
each volume at both of our two locations, most of which get released at =
least once
per day. We are seeing that clients connected to us on the other
end of the T3 (facility B) are randomly losing access to the RO volumes =
(i suspect during
vos releases but not sure). If I cd into the readonly path from the =
clients that are at facility B=20
the directory will be completely empty if I do an ls however the RW path =
will still look fine. At facility A
(closest to the RW copy) the RO path and .readonly volumes display =
contents fine.=20
If I then zap all the read-onlys,re-release, and fs flushvolume on =
clients at facility B
the problem goes away only to reappear with another random volume later =
in=20
the day. This even happens with volumes which had been released to all =
their RO sites
successfully at some point in the past so even if vos release wasn't =
completing I thought
the old data would still be accessible to remote clients closest to =
those RO copies. Anyone have any=20
ideas what might be causing this behavior or where I should look for =
clues?
Christopher Arnold
Pictage, Inc.
------=_NextPart_000_00FD_01C3C094.CF207710
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Recently I've noticed an odd problem in =
our=20
environment and can't seem to</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>track down the source. We =
are=20
running 1.2.10 servers/clients on redhat linux 7.3/8.0 =
in</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>two locations connected via a T3. =
We have 2=20
read-only sites created for</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>each volume at both of our two=20
locations, most of which get released at least once</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>per day. We are =
seeing that clients=20
connected to us on the other</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>end of the T3 (facility B) are randomly =
losing=20
access to the RO volumes (i suspect during</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>vos releases but not sure). =
</FONT><FONT face=3DArial=20
size=3D2>If I cd into the readonly path from the clients that are =
at facility=20
B </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the directory will be completely empty =
if I do=20
an ls however the RW path will still look fine. At facility =
A</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>(closest to the RW copy) the RO path =
and .readonly=20
volumes display contents fine.</FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>If I then zap all the =
read-onlys,re-release, and fs=20
flushvolume on clients at facility B</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the problem goes away only to reappear =
with another=20
random volume later in </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the day. This even happens =
with volumes=20
which had been released to all their RO sites</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>successfully at some point in the past =
so even if=20
vos release wasn't completing I thought</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the old data would still be =
accessible to=20
remote clients closest to those RO copies. Anyone have any =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>ideas what </FONT><FONT face=3DArial =
size=3D2>might be=20
causing this behavior or where I should look for clues?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Christopher Arnold</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Pictage, =
Inc.</FONT></DIV></BODY></HTML>
------=_NextPart_000_00FD_01C3C094.CF207710--