linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Julius <jnews@julius-net.net>
To: linux-raid@vger.kernel.org
Subject: Re: Raid5 with 2 bad drives
Date: Tue, 22 Feb 2005 19:40:02 -0500	[thread overview]
Message-ID: <87fyzoaz31.fsf@julius-net.net> (raw)
In-Reply-To: Pine.LNX.4.56.0502221656160.4157@lion.drogon.net

Gordon Henderson <gordon@drogon.net> writes:

> Try something like:
>
>   mdadm --assemble /dev/mdY /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 \
> 	--run --force

--force did the trick.  I could have thought of that one myself.
Thanks.

As for not hitting the bad blocks again: Is there a way to find out to
which file they belong with ext3/xfs on LVM on RAID5?  That would be
helpfull.

Matthias


  reply	other threads:[~2005-02-23  0:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 16:43 Raid5 with 2 bad drives Matthias Julius
2005-02-22 17:03 ` Gordon Henderson
2005-02-23  0:40   ` Matthias Julius [this message]
2005-02-23  6:23     ` Mike Hardy
2005-02-23 13:35       ` Matthias Julius

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=87fyzoaz31.fsf@julius-net.net \
    --to=jnews@julius-net.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).