[OpenAFS] automatic replication of ro volumes
Steve Simmons
scs@umich.edu
Mon, 12 Nov 2018 14:03:12 -0500
--000000000000711b0c057a7c5a3d
Content-Type: text/plain; charset="UTF-8"
Cron has no more knowledge about when the r/w volume is in a consistent
state than does AFS. Only the person(s) who make the changes to the r/w
volume know when it's ready to release.
Steve Simmons
ITS Unix Support/SCS Admins
On Mon, Nov 12, 2018 at 9:22 AM Andreas Ladanyi <andreas.ladanyi@kit.edu>
wrote:
> Hi Jeffrey,
> >> it is common an openafs admin has to sync an ro volume after something
> >> is added to rw volume. This is done by the vos release command. I think
> >> its the only way. Are there automatic sync functions in the vol / fs
> server.
> > The risk of automated volume releases is that the automated system does
> > not know when the volume contents are in a consistent and quiescent
> state.
>
> ok, but vos release "knows" them ?
>
> Is there something against a crontab script as root with vos lock and
> vos release to all volumes (with an ro site) ?
>
> >
> > Sites often use remctl to grant end users the ability to release their
> > own volumes.
> >
> > Automated releases of RO volumes are a poor substitute for replicated RW
> > volumes. RW replication is a feature which was never completed for
> OpenAFS.
> >
> > Jeffrey Altman
> >
> Andreas
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>
--000000000000711b0c057a7c5a3d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif">Cron has no more knowledge about when the r/w volume is=
in a consistent state than does AFS. Only the person(s) who make the chang=
es to the r/w volume know when it's ready to release.</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br></d=
iv><div><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_=
signature"><div dir=3D"ltr"><div>Steve Simmons<br>ITS Unix Support/SCS Admi=
ns<br></div></div></div></div><br></div><br><div class=3D"gmail_quote"><div=
dir=3D"ltr">On Mon, Nov 12, 2018 at 9:22 AM Andreas Ladanyi <<a href=3D=
"mailto:andreas.ladanyi@kit.edu">andreas.ladanyi@kit.edu</a>> wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">Hi Jeffrey,<br>
>> it is common an openafs admin has to sync an ro volume after somet=
hing<br>
>> is added to rw volume. This is done by the vos release command. I =
think<br>
>> its the only way. Are there automatic sync functions in the vol / =
fs server.<br>
> The risk of automated volume releases is that the automated system doe=
s<br>
> not know when the volume contents are in a consistent and quiescent st=
ate.<br>
<br>
ok, but vos release "knows" them ?<br>
<br>
Is there something against a crontab script as root with vos lock and <br>
vos release to all volumes (with an ro site)=C2=A0 ?<br>
<br>
><br>
> Sites often use remctl to grant end users the ability to release their=
<br>
> own volumes.<br>
><br>
> Automated releases of RO volumes are a poor substitute for replicated =
RW<br>
> volumes.=C2=A0 RW replication is a feature which was never completed f=
or OpenAFS.<br>
><br>
> Jeffrey Altman<br>
><br>
Andreas<br>
_______________________________________________<br>
OpenAFS-info mailing list<br>
<a href=3D"mailto:OpenAFS-info@openafs.org" target=3D"_blank">OpenAFS-info@=
openafs.org</a><br>
<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info" rel=3D"=
noreferrer" target=3D"_blank">https://lists.openafs.org/mailman/listinfo/op=
enafs-info</a><br>
</blockquote></div>
--000000000000711b0c057a7c5a3d--