From: "Mark Cuss" <mcuss@cdlsystems.com>
To: linux-raid-owner@vger.kernel.org
Cc: linux-raid@vger.kernel.org
Subject: Re: How to force a spare drive to take over in a RAID5?
Date: Thu, 11 Aug 2005 10:03:45 -0600 [thread overview]
Message-ID: <006301c59e8e$40d235f0$ab0e10ac@pinchy> (raw)
In-Reply-To: 17147.9289.214312.837092@cse.unsw.edu.au
Oh jeez how obvious - I guess I should've RTFM'd with a little more
attention to detail - sorry 'bout the extremely obvious question!
Mark
----- Original Message -----
From: "Neil Brown" <neilb@cse.unsw.edu.au>
To: "Mark Cuss" <mcuss@cdlsystems.com>
Cc: <linux-raid@vger.kernel.org>
Sent: Thursday, August 11, 2005 4:11 AM
Subject: Re: How to force a spare drive to take over in a RAID5?
> On Tuesday August 9, mcuss@cdlsystems.com wrote:
>> Hmm - Okay. If I do that, I get "/dev/sdr1 does not appear to be an md
>> device". If I add --force with this it doesn't seem to matter.
>>
> ...
>> From: "Mike Tran" <mhtran@us.ibm.com>
>> To: <linux-raid@vger.kernel.org>
>> Sent: Monday, August 08, 2005 4:29 PM
>> Subject: Re: How to force a spare drive to take over in a RAID5?
>>
>>
>> > You're on the right track :) mdadm --fail /dev/sdr should do.
>
> Ofcourse, What Mike meant was
> mdadm /dev/md4 --fail /dev/sdr
>
> NeilBrown
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2005-08-11 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45138.213.188.237.106.1123086677.squirrel@localhost>
2005-08-05 2:58 ` File corruption on LVM2 on top of software RAID1 Andrew Morton
2005-08-05 3:01 ` Andrew Morton
2005-08-05 7:56 ` Simon Matter
2005-08-05 8:02 ` Andrew Morton
2005-08-05 14:31 ` How to force a spare drive to take over in a RAID5? Mark Cuss
2005-08-07 11:29 ` David Greaves
2005-08-08 21:43 ` Mark Cuss
2005-08-08 22:29 ` Mike Tran
2005-08-09 19:48 ` Mark Cuss
2005-08-11 10:11 ` Neil Brown
2005-08-11 16:03 ` Mark Cuss [this message]
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='006301c59e8e$40d235f0$ab0e10ac@pinchy' \
--to=mcuss@cdlsystems.com \
--cc=linux-raid-owner@vger.kernel.org \
--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).