linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ronny Plattner <ronny_p@gmx.net>
To: linux-raid@vger.kernel.org
Subject: Re: once again raid5
Date: Thu, 31 Mar 2005 15:15:33 +0200	[thread overview]
Message-ID: <d2gt2h$ha4$1@sea.gmane.org> (raw)
In-Reply-To: <16971.62329.939077.933653@cse.unsw.edu.au>

Hello,

Neil Brown schrieb:
> It looks like hdi1 doesn't think it is an active part of the array. 
> It is just a spare. 
> It is as-though the array was not fully synced when hdm1 (?) failed.

Mhm.

> Looking back through previous emails, it looks like you had 2 drive
> fail in a raid5 array.  This means you lose. :-(

hdm is since 2 weeks stable with 3 reallocated sectors...so, maybe no 
much data is lost.

> Your best bet would be:
> 
>   mdadm --create /dev/md2 --level 5 -n 4 /dev/hda1 /dev/hdk1 missing  /dev/hdo1
> 
> and hope that the data you find on md2 isn't too corrupted.  You might be

Okay. But, isnt it better to use build instead of create? In the the 
manpages (printed 5.4.2004) ...i can see

-snip-
mdadm -build device ..... -raid-devices=Z devices

This usage is similar to --create. The difference is that it creates a 
legacy array without a superblock. With these arrays there is no 
difference between initially creating the array and subsequently 
assembling the array, except that hopefully there is useful data there 
in the second case.
-snap-

> lucky, but I'm not holding my breath - sorry.

Thank you :-)  ... so, there are no problems with the superblocks?

Regards,
Ronny


  reply	other threads:[~2005-03-31 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 12:41 once again raid5 Ronny Plattner
2005-03-31 12:56 ` Neil Brown
2005-03-31 13:15   ` Ronny Plattner [this message]
2005-04-03 16:56   ` Ronny Plattner

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='d2gt2h$ha4$1@sea.gmane.org' \
    --to=ronny_p@gmx.net \
    --cc=linux-raid@vger.kernel.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).