From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: 2+ raid sets, sata and a missing hd question
Date: Wed, 15 Feb 2006 07:50:28 +0100 [thread overview]
Message-ID: <20060215065028.GA2452@percy.comedia.it> (raw)
In-Reply-To: <20060215024521.GD8282@zip.com.au>
On Wed, Feb 15, 2006 at 01:45:21PM +1100, CaT wrote:
>Seeing as how SATA drives can move around if one removes one from a set
>(ie given sda, sdb, sdc, if sdb was removed sdc drops to sdb) would md6
>come back up without problems if I were to remove either sda or sdb.
if you configured mdadm correctly, you will have no problem :)
hint
echo DEVICE partitions >> /etc/mdadm.conf
mdadm -Esc partitions | grep ARRAY>> /etc/mdadm.conf
>All md partitions are of type fd (Linux raid autodetect).
>
this is surprisingly not at all relevant
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2006-02-15 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 2:45 2+ raid sets, sata and a missing hd question CaT
2006-02-15 6:50 ` Luca Berra [this message]
2006-02-15 10:02 ` CaT
2006-02-15 23:44 ` Mark Hahn
2006-02-16 8:24 ` Luca Berra
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=20060215065028.GA2452@percy.comedia.it \
--to=bluca@comedia.it \
--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).