From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16493 invoked by alias); 8 Apr 2004 07:39:54 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 16477 invoked from network); 8 Apr 2004 07:39:52 -0000 Message-ID: <407501C4.5080500@eCosCentric.com> Date: Thu, 08 Apr 2004 07:39:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.4) Gecko/20030703 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: eCos Maintainers Subject: [Fwd: Re: HEAD update blocked] Content-Type: multipart/mixed; boundary="------------050908020201080200080108" X-SW-Source: 2004-04/txt/msg00000.txt.bz2 This is a multi-part message in MIME format. --------------050908020201080200080108 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-length: 404 I recommend not committing any new patches for the moment. Even without potential corruption of the particular commit, it may be reverted if there's a restore from backup. I'll try to remember to notify folks once things are back to normal. Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine --------------050908020201080200080108 Content-Type: message/rfc822; name="Re: HEAD update blocked" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Re: HEAD update blocked" Content-length: 3232 Received: via dmail-2002(12) for +IMAPdir/Inboxes/Overseers; Thu, 8 Apr 2004 06:37:22 +0100 (BST) Return-Path: Delivered-To: jlarmour@localhost.jifvik.org Received: by jifvik.dyndns.org (Postfix, from userid 40009) id 5DC853FE01; Thu, 8 Apr 2004 06:37:14 +0100 (BST) Delivered-To: jifvikmail@localhost.jifvik.org Received: from localhost (localhost [127.0.0.1]) by jifvik.dyndns.org (Postfix) with ESMTP id EF4683FE01 for ; Thu, 8 Apr 2004 06:37:13 +0100 (BST) Envelope-to: jifloverseers@jifvik.org Delivery-date: Thu, 08 Apr 2004 06:36:52 +0100 Received: from mail.visn.co.uk [195.149.39.183] by localhost with POP3 (fetchmail-5.9.0) for jifvikmail@localhost (single-drop); Thu, 08 Apr 2004 06:37:14 +0100 (BST) Received: from sources.redhat.com ([67.72.78.213]) by gandalf.visn.co.uk with smtp (Exim 3.36 #1) id 1BBSDb-0001nF-00 for jifloverseers@jifvik.org; Thu, 08 Apr 2004 06:36:51 +0100 Received: (qmail 25870 invoked by alias); 8 Apr 2004 05:36:50 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Delivered-To: mailing list overseers@sources.redhat.com Received: (qmail 25863 invoked from network); 8 Apr 2004 05:36:49 -0000 Received: from unknown (HELO molenda.com) (192.220.74.81) by sources.redhat.com with SMTP; 8 Apr 2004 05:36:49 -0000 Received: (qmail 65057 invoked by uid 19025); 8 Apr 2004 05:36:48 -0000 Date: Wed, 7 Apr 2004 22:36:48 -0700 From: Jason Molenda To: law@redhat.com Cc: David Edelsohn , Gabriel Dos Reis , overseers@gcc.gnu.org Subject: Re: HEAD update blocked Message-ID: <20040407223648.A64292@molenda.com> References: <200404080444.i384iCT29856@makai.watson.ibm.com> <200404080520.i385KLqB029126@speedy.slc.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200404080520.i385KLqB029126@speedy.slc.redhat.com>; from law@redhat.com on Wed, Apr 07, 2004 at 11:20:19PM -0600 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on garibaldi.jifvik.org X-Spam-Level: X-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_10 autolearn=no version=2.60 Content-length: 581 On Wed, Apr 07, 2004 at 11:20:19PM -0600, law@redhat.com wrote: > I'd recommend bringing the machine down and forcing an fsck of all the > relevant filesystems. Unfortunately, I'm 1500 miles away and don't > trust myself to set that up and deal with any potential consequences > remotely. A failing disk is a big risk particularly the CVS repository disk. I would not be opposed to turning off all CVS access until some capable RH person can look at it personally tomorrow morning. Opinions? Does anyone know for certain that such a knowledgable person can be found? Jason --------------050908020201080200080108--