[Fwd: Re: HEAD update blocked]

[Jonathan Larmour <jifl at eCosCentric dot com>]

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

--- Begin Message ---

• From: Jason Molenda <jason-gcclist at molenda dot com>
• To: law at redhat dot com
• Cc: David Edelsohn <dje at watson dot ibm dot com>,Gabriel Dos Reis <gdr at integrable-solutions dot net>,overseers at gcc dot gnu dot org
• Date: Wed, 7 Apr 2004 22:36:48 -0700
• Subject: Re: HEAD update blocked
• Delivery-date: Thu, 08 Apr 2004 06:36:52 +0100
• Envelope-to: jifloverseers@jifvik.org
• References: <200404080444.i384iCT29856@makai.watson.ibm.com> <200404080520.i385KLqB029126@speedy.slc.redhat.com>

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

--- End Message ---