From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5469 invoked by alias); 13 Jun 2009 22:00:42 -0000 Received: (qmail 5456 invoked by uid 22791); 13 Jun 2009 22:00:37 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 13 Jun 2009 22:00:33 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 142471519652 for ; Sat, 13 Jun 2009 23:00:30 +0100 (BST) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vn1APK+jtTU5; Sat, 13 Jun 2009 23:00:27 +0100 (BST) Message-ID: <4A34218A.4020501@ecoscentric.com> Date: Sat, 13 Jun 2009 22:00:00 -0000 From: Alex Schuilenburg User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: eCos Maintainers Subject: Bugzilla is back [Was: Bugzilla is down] References: <4A32188E.20508@ecoscentric.com> <4A322F2A.8040305@dallaway.org.uk> In-Reply-To: <4A322F2A.8040305@dallaway.org.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org X-SW-Source: 2009-06/txt/msg00006.txt.bz2 Alex Schuilenburg wrote: > We can recover, but it is a bit of a nasty process involving shrinking > filesystems and RAID drives to below the errors so the resync can > succeed. I will be going down to Telehouse again tonight to install the > second new hard drive, assuming the resizing etc go OK. > Unfortunately this whole process took a lot longer than originally anticipated and was finally completed this morning at 4am BST. Bugzilla is now back online. FYI, things get "interesting" when you have two RAID disks that are failing. Unfortunately the error prevented the filesystem shrink from succeeding and we did not have enough free space to play around with so I manually had to resort to copying off the data onto the first new drive built as part of a partially constructed RAID array, replace the failing drive, reboot the system onto the first new drive and then add 2nd new drive into the array. -- Alex