[OpenAFS] Terminal server/Citrix & AFS Client
Robin Manke-Cassidy
Robin.Manke@asu.edu
Wed, 3 Sep 2008 16:41:46 -0700
--_000_230DD43ACFBCEF49BA88DFD6395AA0414AB08DEE3AEX10asuritead_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
We are running a Citrix farm using AFS as the main storage for the users. =
We have been experiencing some stability issues with the client. I am look=
ing for anyone that is using terminal server or Citrix in a high volume sit=
uation. Here are the symptoms that we are experiencing:
1. No one can get to the S drive, even after a log out and relaunch of an =
app. In this case, we've found that the Service is running, but is complet=
ely non-responsive. AFS space is at this point, completely unusable, and a=
service restart works only 10-20% of the time.
2. The client seems to stop responding while folks are on the server. Tho=
se that attached before the failure seem to be ok. Anyone new coming on a =
server is without an S: drive. 75-90% of the time, a service restart fixes=
the issue.
3. One or two people on a server are unable to get to their S: drive. All=
existing with an S: drive and most to all new sessions get the S: drive. =
This appears to be caused by the client not initializing correctly within t=
he session startup, and is resolved nearly 100% of the time with a logout a=
nd relaunch of the app.
The S: drive is the AFS mounted volume.
Thanks for any feedback or information.
Robin Manke-Cassidy
Arizona State University
University Technology Office
(p) 480-965-5683
robin.manke@asu.edu
--_000_230DD43ACFBCEF49BA88DFD6395AA0414AB08DEE3AEX10asuritead_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:D=3D"DAV:" xmln=
s:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois=3D"ht=
tp://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://schema=
s.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3.org/2=
000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http://www=
.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sharepoin=
t/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" xmlns=
:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://schema=
s.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSc=
hema-instance" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile=
" xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns=
:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns=
:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http=
://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t=3D"ht=
tp://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m=3D"htt=
p://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z=3D"urn:s=
chemas-microsoft-com:" xmlns:st=3D"" 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=3DGenerator content=3D"Microsoft Word 12 (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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal>We are running a Citrix farm using AFS as the main sto=
rage
for the users. We have been experiencing some stability issues with t=
he
client. I am looking for anyone that is using terminal server or Citr=
ix in a
high volume situation. Here are the symptoms that we are experiencing=
:<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>1.
No one can get to the S drive, even after a log out and relaunch of an
app. In this case, we've found that the Service is running, but is
completely non-responsive. AFS space is at this point, completely
unusable, and a service restart works only 10-20% of the time.</span><o:p><=
/o:p></p>
<p class=3DMsoNormal> <o:p></o:p></p>
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>2.
The client seems to stop responding while folks are on the server. Th=
ose
that attached before the failure seem to be ok. Anyone new coming on =
a
server is without an S: drive. 75-90% of the time, a service restart
fixes the issue.</span><o:p></o:p></p>
<p class=3DMsoNormal> <o:p></o:p></p>
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>3.
One or two people on a server are unable to get to their S: drive. Al=
l
existing with an S: drive and most to all new sessions get the S: drive.&nb=
sp;
This appears to be caused by the client not initializing correctly within t=
he
session startup, and is resolved nearly 100% of the time with a logout and
relaunch of the app.</span><o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>The S: drive is the AFS mounted volume.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Thanks for any feedback or information.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Robin Manke-Cassidy<o:p></o:p></p>
<p class=3DMsoNormal>Arizona State University<o:p></o:p></p>
<p class=3DMsoNormal>University Technology Office<o:p></o:p></p>
<p class=3DMsoNormal>(p) 480-965-5683<o:p></o:p></p>
<p class=3DMsoNormal>robin.manke@asu.edu<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
--_000_230DD43ACFBCEF49BA88DFD6395AA0414AB08DEE3AEX10asuritead_--