linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <Paul.Clements@SteelEye.com>
To: Wolfram Schlich <lists@schlich.org>
Cc: Linux-RAID mailinglist <linux-raid@vger.kernel.org>
Subject: Re: I just trashed my RAID5 array - recovery possible?
Date: Thu, 20 Mar 2003 10:32:24 -0500	[thread overview]
Message-ID: <3E79DF08.85CE767@SteelEye.com> (raw)
In-Reply-To: 20030320141907.ALLYOURBASEAREBELONGTOUS.K4264@bla.fasel.org

Wolfram Schlich wrote:
> 
> * Ross Vandegrift <ross@willow.seitz.com> [2003-03-20 14:35]:
> > On Thu, Mar 20, 2003 at 01:22:27PM +0100, Wolfram Schlich wrote:
> > > I've put up the logfile of fsck at
> > > http://wolfram.schlich.org/tmp/fsck.log.1
> > > I have no idea whether this is an "uncomfortable large amount of
> > > damage", so would you mind having a look at it? :-) TIA!
> >
> > That's a pretty huge amount of damage.  If fsck is able to fix it
> > without trashing data, then it doesn't matter.  I missed how big your
> > array was, but if you have the resources to make an image of the raw
> > devices, I'd definately reccomend you do so:
> 
> Unfortunately the array is 4x120G. I just don't have that space
> anywhere else :-(( Anyway, do the *kinds* of errors show these are
> 'critical' ones?

Well, mostly looks like your free block and inode counts are wrong,
which I believe fsck can correct fairly accurately. However, as Ross
said, you have extensive corruption of your filesystem metadata, so the
data very well could be corrupted too, but fsck isn't going to tell you
about that...you'll just have to find out... :). If you can't make a
backup of the disks, I guess you just have to give it a shot, anyway,
right?

--
Paul

  reply	other threads:[~2003-03-20 15:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20  0:03 I just trashed my RAID5 array - recovery possible? Wolfram Schlich
2003-03-20  0:20 ` Neil Brown
2003-03-20  7:10   ` Wolfram Schlich
2003-03-20  7:51   ` Wolfram Schlich
2003-03-20  9:55     ` Neil Brown
2003-03-20 12:22       ` Wolfram Schlich
2003-03-20 13:34         ` Ross Vandegrift
2003-03-20 14:19           ` Wolfram Schlich
2003-03-20 15:32             ` Paul Clements [this message]
2003-03-20 15:46               ` Wolfram Schlich
2003-03-20 17:56       ` Wolfram Schlich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E79DF08.85CE767@SteelEye.com \
    --to=paul.clements@steeleye.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@schlich.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).