[mirror-admin] ERROR: chroot failed for fedora-web

Jesse Keating jkeating at redhat.com
Tue Jan 13 20:36:00 EST 2009


On Tue, 2009-01-13 at 23:01 -0200, Carlos Carvalho wrote:
> On Tue, 13 Jan 2009 14:10:18 -0800 Jesse Keating <jkeating at redhat.com> wrote:
>  >fullfilelist is something we're working on that came from a FUDCon
>  >brainstorming session.
> 
> What's FUDCon?

Fedora Users and Developers Conference

> 
> This is a mirror-only issue, so I think this list is the correct
> forum; why hasn't it been discussed here?

It has been, the discussion came from the desire to switch to Push
Mirroring.  When discussing what value push mirroring would have, we
also explored other ways of reaching that value without resorting to a
push method.  FUDCon gave us the opportunity to have a high bandwidth
(face to face) chat about these things and explore some ideas.

> 
> These are just questions, it's your distribution and you can do
> whatever you see fit with it.
> 
>  >fullfilelist is updated each time we put new content in a top level
>  >module, giving mirrors something they can quickly reference to see if
>  >anything has changed.  This would prevent the full tree walk and
>  >timestamp check / comparison that drives load up and takes a long time
>  >to complete.  Matt Domsch is likely working on a writeup from our
>  >session and I'm still working on the fullfilelist generation scripts.
> 
> I'm happy to see it (finally...) being done. However just names are
> useless, other info is necessary. You don't need any scripts, just
> 
> rsync --exclude /fullfilelist localhost::fedora-enchilada/ > path/fullfilelist
> 
> is enough.

By "scripts" I meant adding the like to the scripts that place content
on the rsync servers.

What "other info" is necessary?  We're generating something that rsync
can consume directly, rather than building up some other infrastructure
around it.

> 
> In fact, I'm already using file lists to avoid dreadful disk
> scavenging here...
> 
> If you want to get fancy you should create a list of checksums. It can
> be used for the same purpose with the added bonus of allowing mirrors
> to check if their repository is correct without having to deal with
> rpm, besides making checking much faster than with it. The best format
> is the one created by *sum family. This would be a most welcome
> improvement to the fedora archive.
> 
> --

Again that would be something that rsync can't consume, and beyond the
scope of what we're trying to address here.  We already have tools that
will compare packages on disk to their checksums in repodata, which can
also verify things like image files, etc...  It should only be necessary
to verify the repomd.xml and .treeinfo files themselves for upstream
checksums, everything else is self checksummed in the trees.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mail.ale.org/pipermail/mirror-admin/attachments/20090113/057edb8f/attachment.bin 
-------------- next part --------------
--


More information about the Mirror-admin mailing list