From: Mark Knecht <markknecht@gmail.com>
To: Linux-RAID <linux-raid@vger.kernel.org>
Subject: 3-drive RAID1 for my low use home server?
Date: Tue, 23 Mar 2010 14:37:26 -0700 [thread overview]
Message-ID: <5bdc1c8b1003231437q1cbeabex85833be0a59e3357@mail.gmail.com> (raw)
Hi,
Just triple checking what I think I've learned here before I start
loading Gentoo. Parts are arriving and I'm staring to put them
together to build a combo low-use server (backups and MythTV) as well
as desktop for my wife. I can do anything up to 6 drives but want the
RAID to survive in the face of possibly two drive failure. This is all
low bandwidth stuff.
I'm fairly focused at this point on doing RAID1 using 3 drives.
Unless I hear differently I believe a 3-drive RAID1 could survive 2
drive failures, and as well any single drive could be taken to another
machine or even placed in an external USB/eSATA drive container in the
event of some major motherboard failure. Is any of that incorrect?
Also, along the way folks have mentioned hot spares but I'm not
seeing that a hot spare does much for RAID1. Am I incorrect about
that? Granted, I guess the rebuild starts automatically and maybe
that's worth it, but I'm thinking that mdadm can probably let me know
fairly quickly that I need to do some work. I've purchased 6 drives so
I'll have 2 or 3 spares around and I can do a hot spare but I don't
see the value in spinning the drive for a year burning power and
wearing the drive out vs. just putting it on the shelf and keeping it
in reserve for a rainy day.
Off to start tearing into packaging. Thanks in advance again for
all the great info I've gotten so far.
Cheers,
Mark
next reply other threads:[~2010-03-23 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 21:37 Mark Knecht [this message]
2010-03-24 14:49 ` 3-drive RAID1 for my low use home server? Eric Shubert
2010-03-24 14:59 ` Mark Knecht
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=5bdc1c8b1003231437q1cbeabex85833be0a59e3357@mail.gmail.com \
--to=markknecht@gmail.com \
--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).