[OpenAFS] Anyone else experiencing a cache bug in 64-bit OpenAFS for Windows
1.7.3200?
Howard Jr, Russell A
russ@cs.pitt.edu
Tue, 25 Nov 2014 15:22:18 +0000
--_000_eb9c910f0a264d2c8374e39c84348ac8pittprodx09univpittedu_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Since October, I've been doing upgrades and new installs of the OpenAFS Cli=
ent using 1.7.3200. We've recently encountered what appears to be a cache-=
related bug in this version but I haven't found a way to reliably reproduce=
it. All clients are running Windows 8 x64 Enterprise as the OS.
When the error occurs, it presents itself by the user seeing the following =
message when trying to access any mapped AFS drives ("M" in this case):
M:\ is not accessible.
The name of the file cannot be resolved by the system.
In order to restore AFS access on the machine, I had to stop the AFS Client=
service, remove the cache file, and restart the service. This is only a t=
emporary fix as we've had several users experience this issue multiple time=
s. Since this appears to be a reoccurring problem, yesterday I tried a dif=
ferent approach. On a machine that was failing, I removed 1.7.3200, reboot=
ed, installed 1.7.3100, and rebooted again. This was done without clearing=
the AFS cache and it restored AFS access.
Has anyone else encountered this problem?
--
Russ Howard
--_000_eb9c910f0a264d2c8374e39c84348ac8pittprodx09univpittedu_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Since October, I’ve been doing upgrades and ne=
w installs of the OpenAFS Client using 1.7.3200. We’ve recently=
encountered what appears to be a cache-related bug in this version but I h=
aven’t found a way to reliably reproduce it. All clients
are running Windows 8 x64 Enterprise as the OS.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">When the error occurs, it presents itself by the use=
r seeing the following message when trying to access any mapped AFS drives =
(“M” in this case):<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoPlainText">M:\ is not accessible.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">The name of the file cannot be resolved by the sy=
stem.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">In order to restore AFS access on the machine, I had=
to stop the AFS Client service, remove the cache file, and restart the ser=
vice. This is only a temporary fix as we’ve had several users e=
xperience this issue multiple times. Since this
appears to be a reoccurring problem, yesterday I tried a different approac=
h. On a machine that was failing, I removed 1.7.3200, rebooted, insta=
lled 1.7.3100, and rebooted again. This was done without clearing the=
AFS cache and it restored AFS access.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Has anyone else encountered this problem?<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">--<o:p></o:p></p>
<p class=3D"MsoNormal">Russ Howard<o:p></o:p></p>
</div>
</body>
</html>
--_000_eb9c910f0a264d2c8374e39c84348ac8pittprodx09univpittedu_--