[mirror-admin] Mirror Prep Consensus?

[Chuck Anderson]

On Tue, Sep 09, 2008 at 04:17:20PM -0700, Jesse Keating wrote:
> On Tue, 2008-09-09 at 11:49 -0700, C.M. Connelly wrote:
> > "CA" == Chuck Anderson 
> > "JK" == Jesse Keating <jkeating at redhat.com>
> > 
> >     CA> The newkey versions of releases/ haven't been provided yet,
> >     CA> but when they are they will be:
> >     CA> 
> >     CA> .../os.newkey .../debug.newkey .../SRPMS.newkey
> >     CA> 
> >     CA> etc. for each spin and architecture under releases/8 and
> >     CA> releases/8.
> > 
> >     JK> We were also planning on staging those full of hardlinks
> >     JK> to the old content for a day or 5 (chmodded so that the
> >     JK> world doesn't see them and wonder wtf .newkey has oldkey
> >     JK> content).
> > 
> > So mirror admins won't have to do anything on our end, right?  The
> > mirror masters will have hard links, the leaf mirrors will pick up
> > those links, and a few days later the links will be replaced with
> > real files and the leaves will sync that material.
> > 
> 
> That's the plan.

Have you tested this plan?  I tried to do this with the updates, and 
it didn't go so well.  It seems the rsync client doesn't know how to 
"break" the hardlinks when the server no longer has the files 
hardlinked.  It then proceeds to overwrite all hardlinked copies 
locally when downloading the new files.  On the next sync, the old 
content will get re-downloaded, overwriting the new files again.  etc. 
in an oscillating loop.

--