On 02/05/2011 08:34 PM, Zac Medico wrote:
On 02/05/2011 02:31 PM, Ryan Hill wrote:
On Sat, 5 Feb 2011 18:04:03 +0100
Luca Longinotti<cht...@longitekk.com>  wrote:

Hi, could any of this cause a (kinda) full resync from the mirrors?
Because an emerge --sync I'm doing now is syncing up _all_ files in the
tree and taking ages on my laptop, on the other hand the emerge --sync
I did yesterday at around 1400 CET just synced the changed files, as
usual... I also tried multiple mirrors, thinking maybe one of them was
the problem, but they all happily continued syncing everything.
At the end of the sync, Portage also processed all the update-files,
which too is strange. All the modification times of the files seem to
have been updated... The date on my system is set correctly, so I can't
really explain why this would suddenly happen, as between yesterday and
today I didn't update Portage or rsync.

I've had this happen twice in a row, last night and today.

The sizes of the snapshot deltas [1] also seem to show an unusually big
change:

  snapshot-20110201-20110202.patch.bz2        02-Feb-2011 19:57  163K
  snapshot-20110202-20110203.patch.bz2        03-Feb-2011 19:57  113K
  snapshot-20110203-20110204.patch.bz2        04-Feb-2011 19:53  1.3M

I guess that something about the master rsync mirror has changed. It
used to be osprey.gentoo.org, but the size of the
snapshot-20110203-20110204.patch.bz2 file on osprey is only 107213 bytes.

I can imagine that the first delta has a large changeset because of the process involved. However, it looks normal now, again. It is just part of the upgrade path of changing the service to a new host [that does things ever so slightly different].

120K    snapshot-20110202-20110203.patch.bz2
1.4M    snapshot-20110203-20110204.patch.bz2
260K    snapshot-20110204-20110205.patch.bz2
124K    snapshot-20110205-20110206.patch.bz2

As for the "re-syncing all files thing" - I can't reproduce that, though I've seen multiple reports. Did it settle down now? (I assume so)

-Jeremy

Reply via email to