centoso4 just tried to nuke my 5.5 tree. Thank heaven for --dry-run.
DR
Am 13.05.10 23:45, schrieb David Richardson:
centoso4 just tried to nuke my 5.5 tree. Thank heaven for --dry-run.
Strange.
It is missing the 64 bit DVD iso at the moment (if you are allowed to sync the DVD), but otherwise the 5.5 tree is complete.
21G for 5.5, 25G for 5.5 with DVD.
Ralph
Last ran the rsync agasint centosq2 1 hour ago, and the total folder size is 21G. The missing file problem is now fixed. Thanks!
However, do we have to register our IP with "msync-dvd" to get the DVD ISOs? We would like to carry them, if possible.
Regards HASSAN
On Fri, May 14, 2010 at 03:49, Ralph Angenendt ralph.angenendt@gmail.comwrote:
Am 13.05.10 23:45, schrieb David Richardson:
centoso4 just tried to nuke my 5.5 tree. Thank heaven for --dry-run.
Strange.
It is missing the 64 bit DVD iso at the moment (if you are allowed to sync the DVD), but otherwise the 5.5 tree is complete.
21G for 5.5, 25G for 5.5 with DVD.
Ralph _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
On Thu, 13 May 2010, Ralph Angenendt wrote:
Am 13.05.10 23:45, schrieb David Richardson:
centoso4 just tried to nuke my 5.5 tree. Thank heaven for --dry-run.
Strange.
It is missing the 64 bit DVD iso at the moment (if you are allowed to sync the DVD), but otherwise the 5.5 tree is complete.
21G for 5.5, 25G for 5.5 with DVD.
I have 25G in my 5.5 tree (I have access to the DVDs).
I just tried it again, with the same results. centoso4 tries to delete my 5.5 tree, centosf3 doesn't attempt any changes.
I'm using the command: rsync --dry-run --progress -aHv --delete --delete-excluded --delete-after --delay-updates rsync://msync-dvd.centos.org/CentOS-incdvd/ /pub/centos/
DR
Am 13.05.10 23:57, schrieb David Richardson:
I just tried it again, with the same results. centoso4 tries to delete my 5.5 tree, centosf3 doesn't attempt any changes.
I'm using the command: rsync --dry-run --progress -aHv --delete --delete-excluded --delete-after --delay-updates rsync://msync-dvd.centos.org/CentOS-incdvd/ /pub/centos/
Yupp. That had a puppet process hanging and because of that had an old rsyncd.conf.
This is fixing itself right now. Thanks for reporting.
The problem should be gone in a few minutes.
Ralph
On Thu, 13 May 2010, David Richardson wrote:
centoso4 just tried to nuke my 5.5 tree. Thank heaven for --dry-run.
I did not pay heed and have paid the price; centosr3 just wiped out everything in our (=ftp.iitm.ac.in) 5.5 tree except for some crud in the x86_64 isos directory. Trying resync, seems to be coming through ok from centosx3; it will take a day or two to repopulate ...
It would appear that there is a miserable failure of the master mirrors system whereby some incomplete (and almost empty) mirrors have made it to the list. I volunteer to be a part of whichever team does this so this kind of stuff NEVER happens again. Where do I sign up?
On Fri, 14 May 2010, Prof. P. Sriram wrote:
It would appear that there is a miserable failure of the master mirrors system whereby some incomplete (and almost empty) mirrors have made it to
'miserable failure' ... yeah -- there's a great motivator for the people working for free to provide a product
How about considering a local failure to set downloads into a test location, other the production one, after notice and warning that mirror skew exists. Isn't there some local responsibility for people who are obsessing about this for whatever reason.
If BW is pricey, drop out for a couple days until skew reports stop and the seeding is largely complete
naw ...
-- Russ herrold
On Thu, 13 May 2010, R P Herrold wrote:
'miserable failure' ... yeah -- there's a great motivator for the people working for free to provide a product
why not read the next line of my mail also, where I am offering to join up this group of people working for free?
If BW is pricey, drop out for a couple days until skew reports stop and the seeding is largely complete
yes, bw is pricey in some locales; why couple of days, i would be happy to drop out of the mirror system altogether. it is not just a matter of skew. public mirrors are given a round robin master mirror system - why announce and ask public mirror maintainers to prepare and seed the release before the round robin masters are all seeded and up? maybe, 'miserable failure' is too harsh a term, i apologize, but it appears there is more than an isolated random failure.
On 05/14/2010 04:29 AM, Prof. P. Sriram wrote:
I volunteer to be a part of whichever team does this so this kind of stuff NEVER happens again. Where do I sign up?
I've always wanted to add a --recycle_folder option to rsync:
Files deleted by rsync should instead of being deleted moved to that folder. When the file appears again rsync can just fetch it from the recycle folder. The recycle folder should be cleaned after, say 7 days.
However, I was warned by someone who had taken a closer look at the rsync source: It is difficult to read (write only) :-)
Mogens
On Fri, May 14, 2010 at 8:57 AM, Mogens Kjaer mk@crc.dk wrote:
On 05/14/2010 04:29 AM, Prof. P. Sriram wrote:
I volunteer to be a part of whichever team does this so this kind of stuff NEVER happens again. Where do I sign up?
I've always wanted to add a --recycle_folder option to rsync:
Files deleted by rsync should instead of being deleted moved to that folder. When the file appears again rsync can just fetch it from the recycle folder. The recycle folder should be cleaned after, say 7 days.
--backup-* does at least the saving part for you, the cleaning part can be done via find. Only the fetching part isn't there, it seems :)
Cheers,
Ralph
On Fri, May 14, 2010 at 4:29 AM, Prof. P. Sriram sriram@ae.iitm.ac.in wrote:
On Thu, 13 May 2010, David Richardson wrote:
centoso4 just tried to nuke my 5.5 tree. Thank heaven for --dry-run.
I did not pay heed and have paid the price; centosr3 just wiped out everything in our (=ftp.iitm.ac.in) 5.5 tree except for some crud in the x86_64 isos directory.
Yeah, same problem as with o3. Stuck puppet job, so old configuration. No idea why those are hanging, probably due to timeouts because of 5.5 syncing.
Ralph
On 05/14/2010 03:29 AM, Prof. P. Sriram wrote:
kind of stuff NEVER happens again. Where do I sign up?
If you really want to make a difference :
http://git.chasmd.org/cgit.cgi/chasmd/
- KB
msync.CentOS.org rsync service (centosn4) --------------------------------------- This service is intended for the sole use of the CentOS worldwide mirror network to synchronize mirrors. ... receiving file list ... done ./ TIME timestamp.txt 5.5/isos/x86_64/.CentOS-5.5-x86_64-bin-4of8.iso.qshIqJ
msync.CentOS.org rsync service (centosg4) --------------------------------------- This service is intended for the sole use of the CentOS worldwide mirror network to synchronize mirrors. ... receiving file list ... done ./ TIME timestamp.txt 5.5/isos/x86_64/.CentOS-5.5-x86_64-bin-5of8.iso.dvFrr5
On Wed, May 19, 2010 at 05:09:27PM +0530, Prof. P. Sriram wrote:
msync.CentOS.org rsync service (centosg4)
This service is intended for the sole use of the CentOS worldwide mirror network to synchronize mirrors. ... receiving file list ... done ./ TIME timestamp.txt 5.5/isos/x86_64/.CentOS-5.5-x86_64-bin-5of8.iso.dvFrr5
Thanks for the heads up, file removed.
Tru
msync.CentOS.org rsync service (centosf4) ... receiving file list ... done ./ TIME timestamp.txt 5.5/isos/x86_64/.CentOS-5.5-x86_64-bin-4of8.iso.qshIqJ
On Thu, May 27, 2010 at 02:27:41PM +0530, Prof. P. Sriram wrote:
msync.CentOS.org rsync service (centosf4) ... receiving file list ... done ./ TIME timestamp.txt 5.5/isos/x86_64/.CentOS-5.5-x86_64-bin-4of8.iso.qshIqJ
removed, thanks!
Tru
-
David Richardson -
Karanbir Singh -
Mogens Kjaer -
Nyamul Hassan -
Prof. P. Sriram -
R P Herrold -
Ralph Angenendt -
Tru Huynh