From: Maurice Hilarius <maurice@harddata.com>
To: Chris Murphy <lists@colorremedies.com>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Creating a RAID10 (near) for use in a CentOS 6 system
Date: Mon, 25 Mar 2013 18:47:10 -0600 [thread overview]
Message-ID: <5150F00E.4060506@harddata.com> (raw)
In-Reply-To: <843EA420-6F4A-41DF-BDED-7F35D6263A87@colorremedies.com>
On 3/25/2013 6:40 PM, Chris Murphy wrote:
> On Mar 25, 2013, at 6:05 PM, maurice <mhilarius@gmail.com> wrote:
>> What about partitioning the drives first, installing a smallish partition for boot, then a second much larger partition on each for the RAID10?
> What's the advantage of this compared to a separate drive? In your proposed scenario, if the /boot drive dies, you have an unbootable system anyway.
Firstly, there would be 4 redundant copies of the boot. Easy enough to
accomplish. If any one goes down, easy to pick one of the others.
Secondly, there is only room for 4 drives in this chassis
Thirdly, cost
Now, back to my original question:
Making the RAID10, near.
In reading the man pages, it seems near 2 is the default option for create?
Is there any reason to be wary of the stock CentOS 6 2.6.32 kernel?
--
Cheers,
Maurice Hilarius
eMail: /mhilarius@gmail.com/
next prev parent reply other threads:[~2013-03-26 0:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 17:30 Creating a RAID10 (near) for use in a CentOS 6 system maurice
2013-03-25 17:57 ` maurice
2013-03-25 23:05 ` Chris Murphy
2013-03-25 23:21 ` maurice
2013-03-25 23:44 ` Chris Murphy
2013-03-26 0:05 ` maurice
2013-03-26 0:40 ` Chris Murphy
2013-03-26 0:47 ` Maurice Hilarius [this message]
2013-03-26 1:05 ` Chris Murphy
[not found] ` <5150F101.6020205@gmail.com>
2013-03-26 1:11 ` Chris Murphy
2013-03-26 9:35 ` Brad Campbell
2013-03-26 15:16 ` maurice
2013-03-26 20:21 ` Roy Sigurd Karlsbakk
2013-03-26 20:30 ` Maurice Hilarius
2013-03-26 20:37 ` Roy Sigurd Karlsbakk
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=5150F00E.4060506@harddata.com \
--to=maurice@harddata.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.