From owner-freebsd-questions@FreeBSD.ORG Sat Jan 3 00:20:29 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7091310656DA for ; Sat, 3 Jan 2009 00:20:29 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 38F8C8FC1D for ; Sat, 3 Jan 2009 00:20:29 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 31365 invoked by uid 89); 3 Jan 2009 00:32:23 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 3 Jan 2009 00:32:22 -0000 Message-ID: <495EAF4C.7080105@ibctech.ca> Date: Fri, 02 Jan 2009 19:20:28 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Ian Lord References: <495EA9C1.9090106@ibctech.ca> <9DCBDCBB6388493FA7B2A4262E3E6E6A@msdi.local> In-Reply-To: <9DCBDCBB6388493FA7B2A4262E3E6E6A@msdi.local> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Urgent help needed please: Gvinum problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jan 2009 00:20:30 -0000 Ian Lord wrote: >> Does anyone knows what I can try to try to put back system online (at > least, >> so I can restore a backup on the disk) > > I'm trying to find my vinum notes, but can't as of yet... > > What does a: > > # fsck -y /dev/gvinum/RAID5 > > ...yield...anything? > > Steve > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Same :( > > But thanks all, I just did a newfs and currently restoring backups on it > > Strange... Last time I will will gvinum, nothing as stable as a hardware > controller I guess :( Good job on keeping backups. Hardware is just as apt to fail as software is. I don't care what anyone says. Here's a mantra to stick by. I'm sure others will concur. - do backups (archive, and availability type) - verify integrity - do more backups (hot and storage) - restore backups to test gear - make sure all live and archive backups restore properly, and efficiently People put too much emphasis on backup (even though unfortunately not enough do it at all). The real emphasis should not be put on having a backup, it should be placed squarely on how quickly can you restore from one. Glad you are getting back into operation. For those who may please, a colleague of mine pointed out a decent 'backup' mis-understanding disaster just today on slashdot to me... Also, kids, think about it this way, regardless if you use hardware or software storage mechanisms. If you can't perform the following command on one of your critical servers and restore the data, you're doing it wrong...you need to ask further questions: # rm -rf Seriously. This is a great opportunity to get everyone aware of what a 'backup' actually is. Happy new year all, and let all of your data failures be recoverable! Steve