[mirror-admin] Fedora 11 Beta coming your way

[J.H.]

Carlos,

It might be worth checking in at 
https://fedoraproject.org/wiki/Infrastructure/Mirroring/Tiering it's 
possible that the two mirrors your pointing to just aren't handling the 
load, or don't have good solid connectivity to your location.  Check 
around see if any of the other tier [01] mirrors there are better for you.

If your a public mirror, and your getting blocked, check with Duke and 
check your ACL in mirrormanager.  It's also possible your using a public 
rsync module vs. a mirror module (we have a separate module at 
kernel.org for mirrors to use that gives them access to everything)

Hopefully something there will help.

- John 'Warthog9' Hawley
Chief Kernel.org Administrator

Carlos Carvalho wrote:
> Jesse Keating (jkeating at redhat.com) wrote on 27 March 2009 17:06:
>  >I'm about to flip the bit on Fedora 11 Beta content
>  >(pub/fedora/linux/releases/test/11-Beta/).  du says 48G, give or take
>  >some due to hardlinks with pub/fedora/linux/development/.
>  >
>  >Release date is Tuesday March 31st at 1400 UTC.
>  >
>  >We're also unfreezing rawhide tonight so there will also be a fair
>  >amount of churn in the development/ directory.  Normally I wouldn't do
>  >both at the same time, but this freeze has been too long as it is and we
>  >need to move on.
> 
> This is a disaster for us. Our bandwidth with the master is small,
> just 250KB/s. When you mix development and releases the download is
> enourmous and it takes *very long* just to reach the release, because
> rsync pulls it after development. And we cannot pull just the release
> because of the hardlinks.
> 
> We normally update from Duke, which is 4-5 times faster for us.
> However Duke blocks the new stuff before the release moment so we
> cannot get it anyway. I tried to get development from Duke, then get
> the release from the master but some 20 hours after your announcement
> Duke *still* hadn't the development updates. So a combination of big
> changes + small bandwidth with the master + slowness in Duke made
> things hard here.
> 
> For next time I suggest you wait 2 days before unfreezing development.
> This way we can sync devel from the faster mirror and get the release
> from the master before the unfreeze. Then we go back to the faster
> tier 0 and get the new devel.
> 
> What happened to the internet2 connection of the master(s)? We can get
> more than 4MB/s with the Oregon gigapop...
> 
> --

--