[OpenAFS] Re: Quickie: server prefs

Timothy Balcer timothy@telmate.com
Fri, 20 Dec 2013 21:10:51 -0800


--047d7b6d99b0283e7804ee046baf
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

server 1.6.1 and client 1.6.2, client 1.6.1 both ubuntu and CentOS standard
distribution. It was tested from multiple clients.

VLServer is 1.6.1 ubuntu.

As I said previously, it was evaluated from the RO path.

/afs/domain.com/photos

to be specific. No 'dot'.

Thanks in advance for any help :-) I am looking for troubleshooting steps
to go beyond this.

Hmm... I'll do a bit more looking. I didn't realize that any RW volume in
the path would cause all lookups to be RW. However, as far as I know, I
haven't mounted anything in that path RW on the RO path.



On Fri, Dec 20, 2013 at 7:42 PM, Jeffrey Altman <
jaltman@your-file-system.com> wrote:

> Basic questions.
>
> Which client platform and version?
>
> Is the mount point to the volume being evaluated from a rw volume
> instance?  Once a rw volume is encountered in the path all volume access
> will be to the rw volume.  (unless a mount point is explicitly to the
> volume.readonly.)
>
>
>
>
> On 12/20/2013 7:11 PM, Timothy Balcer wrote:
> > =CB=87To be more clear.. the problematic server (one I was salvaging) h=
ad thr
> > RW/RO pair, and was pref 5005. I set it to 35000 through fs
> > getserverprefs > /tmp/foo, editing that file, and reissuing it through
> > fs setserverprefs -stdin. The other Fileservers which had RO copies wer=
e
> > now at about 20000.
> >
> > It still went for the 35000 pref server.
> >
> >
> > On Fri, Dec 20, 2013 at 3:10 PM, Timothy Balcer <timothy@telmate.com
> > <mailto:timothy@telmate.com>> wrote:
> >
> >     I took down a file server for salvaging today, part of routine
> >     maintenance. It had a RW/RO pair on it of volume 'photos', and ther=
e
> >     were two RO copies on two other fileservers (on other
> >     networks).These RO copies are mounted and online.
> >
> >     When the salvage process started, nothing could talk to the RO path
> >     to the mount. Got some 'Device doesn't exist' sort of errors. Even
> >     on the remote network fileservers.
> >
> >     VLDB entries are clean. Releases are all congruent.
> >
> >     Tried manually setting pref via fs setserverprefs.. set that server
> >     pref to 35000
> >
> >     Still tries to access the local RW/RO volume for the RO path.. doin=
g
> >     an strace showed this was true.
> >
> >     The problem will fix itself once the salvage is over, but this is
> >     disturbing... what can I do to avoid this sort of problem in future=
?
> >     Am I doing something wrong here? Better troubleshooting? Advice
> >     appreciated :)
> >
> >     --
> >     Timothy Balcer / IT Services
> >     Telmate / San Francisco, CA
> >     Direct / (415) 300-4313 <tel:%28415%29%20300-4313>
> >     Customer Service / (800) 205-5510
> >
> >
> >
> >
> > --
> > Timothy Balcer / IT Services
> > Telmate / San Francisco, CA
> > Direct / (415) 300-4313
> > Customer Service / (800) 205-5510
>
>


--=20
Timothy Balcer / IT Services
Telmate / San Francisco, CA
Direct / (415) 300-4313
Customer Service / (800) 205-5510

--047d7b6d99b0283e7804ee046baf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div>server 1.6.1 and client 1.6.2, cl=
ient 1.6.1 both ubuntu and CentOS standard distribution. It was tested from=
 multiple clients.<br><br>VLServer is 1.6.1 ubuntu.<br><br></div>As I said =
previously, it was evaluated from the RO path.<br>
<br></div>/afs/<a href=3D"http://domain.com/photos">domain.com/photos</a><b=
r><br></div>to be specific. No &#39;dot&#39;.<br><br></div>Thanks in advanc=
e for any help :-) I am looking for troubleshooting steps to go beyond this=
.<br>
<br></div>Hmm... I&#39;ll do a bit more looking. I didn&#39;t realize that =
any RW volume in the path would cause all lookups to be RW. However, as far=
 as I know, I haven&#39;t mounted anything in that path RW on the RO path.<=
br>
<div><div><br></div></div></div><div class=3D"gmail_extra"><br><br><div cla=
ss=3D"gmail_quote">On Fri, Dec 20, 2013 at 7:42 PM, Jeffrey Altman <span di=
r=3D"ltr">&lt;<a href=3D"mailto:jaltman@your-file-system.com" target=3D"_bl=
ank">jaltman@your-file-system.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Basic questions.<br>
<br>
Which client platform and version?<br>
<br>
Is the mount point to the volume being evaluated from a rw volume<br>
instance? =C2=A0Once a rw volume is encountered in the path all volume acce=
ss<br>
will be to the rw volume. =C2=A0(unless a mount point is explicitly to the<=
br>
volume.readonly.)<br>
<div class=3D"im"><br>
<br>
<br>
<br>
On 12/20/2013 7:11 PM, Timothy Balcer wrote:<br>
&gt; =CB=87To be more clear.. the problematic server (one I was salvaging) =
had thr<br>
&gt; RW/RO pair, and was pref 5005. I set it to 35000 through fs<br>
&gt; getserverprefs &gt; /tmp/foo, editing that file, and reissuing it thro=
ugh<br>
&gt; fs setserverprefs -stdin. The other Fileservers which had RO copies we=
re<br>
&gt; now at about 20000.<br>
&gt;<br>
&gt; It still went for the 35000 pref server.<br>
&gt;<br>
&gt;<br>
&gt; On Fri, Dec 20, 2013 at 3:10 PM, Timothy Balcer &lt;<a href=3D"mailto:=
timothy@telmate.com">timothy@telmate.com</a><br>
</div><div class=3D"im">&gt; &lt;mailto:<a href=3D"mailto:timothy@telmate.c=
om">timothy@telmate.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 I took down a file server for salvaging today, part of r=
outine<br>
&gt; =C2=A0 =C2=A0 maintenance. It had a RW/RO pair on it of volume &#39;ph=
otos&#39;, and there<br>
&gt; =C2=A0 =C2=A0 were two RO copies on two other fileservers (on other<br=
>
&gt; =C2=A0 =C2=A0 networks).These RO copies are mounted and online.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 When the salvage process started, nothing could talk to =
the RO path<br>
&gt; =C2=A0 =C2=A0 to the mount. Got some &#39;Device doesn&#39;t exist&#39=
; sort of errors. Even<br>
&gt; =C2=A0 =C2=A0 on the remote network fileservers.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 VLDB entries are clean. Releases are all congruent.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 Tried manually setting pref via fs setserverprefs.. set =
that server<br>
&gt; =C2=A0 =C2=A0 pref to 35000<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 Still tries to access the local RW/RO volume for the RO =
path.. doing<br>
&gt; =C2=A0 =C2=A0 an strace showed this was true.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 The problem will fix itself once the salvage is over, bu=
t this is<br>
&gt; =C2=A0 =C2=A0 disturbing... what can I do to avoid this sort of proble=
m in future?<br>
&gt; =C2=A0 =C2=A0 Am I doing something wrong here? Better troubleshooting?=
 Advice<br>
&gt; =C2=A0 =C2=A0 appreciated :)<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 --<br>
&gt; =C2=A0 =C2=A0 Timothy Balcer / IT Services<br>
&gt; =C2=A0 =C2=A0 Telmate / San Francisco, CA<br>
</div>&gt; =C2=A0 =C2=A0 Direct / <a href=3D"tel:%28415%29%20300-4313" valu=
e=3D"+14153004313">(415) 300-4313</a> &lt;tel:%28415%29%20300-4313&gt;<br>
<div class=3D"HOEnZb"><div class=3D"h5">&gt; =C2=A0 =C2=A0 Customer Service=
 / <a href=3D"tel:%28800%29%20205-5510" value=3D"+18002055510">(800) 205-55=
10</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Timothy Balcer / IT Services<br>
&gt; Telmate / San Francisco, CA<br>
&gt; Direct / <a href=3D"tel:%28415%29%20300-4313" value=3D"+14153004313">(=
415) 300-4313</a><br>
&gt; Customer Service / <a href=3D"tel:%28800%29%20205-5510" value=3D"+1800=
2055510">(800) 205-5510</a><br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br><span style=
=3D"border-collapse:collapse;color:rgb(102,102,102);font-family:verdana,san=
s-serif;font-size:x-small">Timothy Balcer / IT Services<br>Telmate / San Fr=
ancisco, CA<br>
Direct / </span><span style=3D"border-collapse:collapse;font-family:verdana=
,sans-serif;font-size:x-small"><font color=3D"#1155cc">(415) 300-4313</font=
><br><font color=3D"#666666">Customer Service /=C2=A0</font><a value=3D"+18=
002055510" style=3D"color:rgb(17,85,204)">(800) 205-5510</a></span>
</div>

--047d7b6d99b0283e7804ee046baf--