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

[Carlos Carvalho]

On Tue, 13 Jan 2009 17:36:00 -0800 Jesse Keating <jkeating at redhat.com> wrote:
 >>  >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.

I'm not sure of what you mean by "the like" but it's not what I said,
otherwise it'd already have the info.

 >What "other info" is necessary?

That provided by rsync.

 >We're generating something that rsync can consume directly, rather
 >than building up some other infrastructure around it.

What do you mean by "rsync can consume"? Using the filelist generated
by rsync has the info

 >> 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.

I'd like to learn how to do it. It's useful to check for data
corruption on the filesystem. Note that the tools should not need to
open the .rpm files because this isn't necessary to check their
integrity.

--