[OpenAFS] new RW root.cell
Susan Litzinger
susan@psc.edu
Thu, 7 Mar 2019 11:29:23 -0500
--00000000000099bc660583839cb7
Content-Type: text/plain; charset="UTF-8"
In order to get our current installation in sync, I attempted to create
another RO root.cell on velma in the same partition that the RW is on but I
am unable to do that and get the error that Multiple ROs on a single server
aren't allowed. Will I cause problems if I remove the current RO (that is
on the wrong partition) then create a new one in the correct partition?
Then, if we move the RW root.cell to afs-vmc, the release should work?
Here is the results of 'vos examine root.cell' for our site:
[root@afs-vmc 2019-March]# vos examine root.cell
vsu_ClientInit: Could not get afs tokens, running unauthenticated.
root.cell 537176384 RW 49 K On-line
velma.psc.edu /vicepca
RWrite 537176384 ROnly 0 Backup 537176401
MaxQuota 20000 K
Creation Tue Nov 29 19:01:08 2005
Copy Fri Jun 8 16:24:57 2012
Backup Sat Mar 2 02:32:38 2019
Last Access Thu Mar 7 10:43:30 2019
Last Update Thu Apr 5 14:20:25 2018
239 accesses in the past day (i.e., vnode references)
RWrite: 537176384 ROnly: 537176385 Backup: 537176401
number of sites -> 5
server velma.psc.edu partition /vicepca RW Site
server daphne.psc.edu partition /vicepdc RO Site
server velma.psc.edu partition /vicepcb RO Site
server scooby.psc.edu partition /vicepac RO Site
server afs-vmc.psc.edu partition /vicepga RO Site -- Not released
Thanks for the help -- Susan
On Wed, Mar 6, 2019 at 6:11 PM Jeffrey Altman <jaltman@auristor.com> wrote:
> On 3/6/2019 3:56 PM, Susan Litzinger wrote:
> > We are updating our very old AFS servers and chose to create new,
> > updated systems then migrate all the volumes over and eventually just
> > turn the older ones off.
> >
> > We've moved everything but the root.cell volumes. We have one RW
> > root.cell on an older server and would like to have a RW root.cell on a
> > new server before turning the older one off. My co-worker gave this a
> > try and it allowed her to run 'vos addsite' but did not allow her to
> > 'vos release' the new RW root.cell. She got this error:
> >
> > root@afs-vmc 2019-March]# vos addsite afs-vmc.psc.edu
> > <http://afs-vmc.psc.edu> /vicepga
> > root.cell -localauth
> > Added replication site afs-vmc.psc.edu <http://afs-vmc.psc.edu> /vicepga
> > for volume root.cell
> > [root@afs-vmc 2019-March]# vos release root.cell -localauth
> > Failed to clone the volume 537176384
> > : Invalid cross-device link
> > Error in vos release command.
> > Clone volume is not in the same partition as the read-write volume.
>
>
> Susan,
>
> The problem with root.cell is on velma. The RW and RO must be on the
> same partition.
>
> Jeffrey Altman
>
>
--00000000000099bc660583839cb7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr"><div>In order to get our current installa=
tion in sync, I attempted to create another RO root.cell on velma in the sa=
me partition that the RW is on but I am unable to do that and get the error=
that Multiple ROs on a single server aren't allowed.=C2=A0 Will I caus=
e problems if I remove the current RO (that is on the wrong partition) then=
create a new one in the correct partition?=C2=A0=C2=A0</div><div><br></div=
><div>Then, if we move the RW root.cell to afs-vmc, the release should work=
?=C2=A0 Here is the results of 'vos examine root.cell' for our site=
:=C2=A0</div><div><br></div><div>[root@afs-vmc 2019-March]# vos examine roo=
t.cell</div><div>vsu_ClientInit: Could not get afs tokens, running unauthen=
ticated.</div><div>root.cell=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0537176384 RW=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A049 K=C2=A0 On-line</div><div>=C2=A0 =C2=A0 <a href=3D"http=
://velma.psc.edu" target=3D"_blank">velma.psc.edu</a> /vicepca=C2=A0</div><=
div>=C2=A0 =C2=A0 RWrite=C2=A0 537176384 ROnly=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 0 Backup=C2=A0 537176401=C2=A0</div><div>=C2=A0 =C2=A0 MaxQuota=C2=
=A0 =C2=A0 =C2=A0 20000 K=C2=A0</div><div>=C2=A0 =C2=A0 Creation=C2=A0 =C2=
=A0 Tue Nov 29 19:01:08 2005</div><div>=C2=A0 =C2=A0 Copy=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 Fri Jun=C2=A0 8 16:24:57 2012</div><div>=C2=A0 =C2=A0 Backup=C2=
=A0 =C2=A0 =C2=A0 Sat Mar=C2=A0 2 02:32:38 2019</div><div>=C2=A0 =C2=A0 Las=
t Access Thu Mar=C2=A0 7 10:43:30 2019</div><div>=C2=A0 =C2=A0 Last Update =
Thu Apr=C2=A0 5 14:20:25 2018</div><div>=C2=A0 =C2=A0 239 accesses in the p=
ast day (i.e., vnode references)</div><div><br></div><div>=C2=A0 =C2=A0 RWr=
ite: 537176384=C2=A0 =C2=A0 =C2=A0ROnly: 537176385=C2=A0 =C2=A0 =C2=A0Backu=
p: 537176401=C2=A0</div><div>=C2=A0 =C2=A0 number of sites -> 5</div><di=
v>=C2=A0 =C2=A0 =C2=A0 =C2=A0server <a href=3D"http://velma.psc.edu" target=
=3D"_blank">velma.psc.edu</a> partition /vicepca RW Site=C2=A0</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0server <a href=3D"http://daphne.psc.edu" target=
=3D"_blank">daphne.psc.edu</a> partition /vicepdc RO Site=C2=A0</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0server <a href=3D"http://velma.psc.edu" target=
=3D"_blank">velma.psc.edu</a> partition /vicepcb RO Site=C2=A0</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0server <a href=3D"http://scooby.psc.edu" target=
=3D"_blank">scooby.psc.edu</a> partition /vicepac RO Site=C2=A0</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0server <a href=3D"http://afs-vmc.psc.edu" target=
=3D"_blank">afs-vmc.psc.edu</a> partition /vicepga RO Site=C2=A0 -- Not rel=
eased</div><div><br></div><div>Thanks for the help -- Susan=C2=A0</div><div=
><br></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Wed, Mar 6, 2019 at 6:11 PM Jeffrey Altman <<a href=
=3D"mailto:jaltman@auristor.com" target=3D"_blank">jaltman@auristor.com</a>=
> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 3=
/6/2019 3:56 PM, Susan Litzinger wrote:<br>
> We are updating our very old AFS servers and chose to create new,<br>
> updated systems then migrate all the volumes over and eventually just<=
br>
> turn the older ones off.=C2=A0<br>
> <br>
> We've moved everything but the root.cell volumes.=C2=A0 We have on=
e RW<br>
> root.cell on an older server and would like to have a RW root.cell on =
a<br>
> new server before turning the older one off.=C2=A0 My co-worker gave t=
his a<br>
> try and it allowed her to run 'vos addsite' but did not allow =
her to<br>
> 'vos release' the new RW root.cell.=C2=A0 She got this error:=
=C2=A0<br>
> <br>
> root@afs-vmc 2019-March]# vos addsite <a href=3D"http://afs-vmc.psc.ed=
u" rel=3D"noreferrer" target=3D"_blank">afs-vmc.psc.edu</a><br>
> <<a href=3D"http://afs-vmc.psc.edu" rel=3D"noreferrer" target=3D"_b=
lank">http://afs-vmc.psc.edu</a>> /vicepga=C2=A0<br>
> root.cell -localauth<br>
> Added replication site <a href=3D"http://afs-vmc.psc.edu" rel=3D"noref=
errer" target=3D"_blank">afs-vmc.psc.edu</a> <<a href=3D"http://afs-vmc.=
psc.edu" rel=3D"noreferrer" target=3D"_blank">http://afs-vmc.psc.edu</a>>=
; /vicepga<br>
> for volume root.cell<br>
> [root@afs-vmc 2019-March]# vos release root.cell -localauth<br>
> Failed to clone the volume 537176384<br>
> : Invalid cross-device link<br>
> Error in vos release command.<br>
> Clone volume is not in the same partition as the read-write volume.<br=
>
<br>
<br>
Susan,<br>
<br>
The problem with root.cell is on velma.=C2=A0 The RW and RO must be on the<=
br>
same partition.<br>
<br>
Jeffrey Altman<br>
<br>
</blockquote></div>
--00000000000099bc660583839cb7--