From: keld@keldix.com
To: Miles Fidelman <mfidelman@meetinghouse.net>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: md RAID10 questions
Date: Tue, 11 Oct 2011 00:15:47 +0200 [thread overview]
Message-ID: <20111010221547.GA30555@www5.open-std.org> (raw)
In-Reply-To: <4E93657F.1090500@meetinghouse.net>
On Mon, Oct 10, 2011 at 05:37:03PM -0400, Miles Fidelman wrote:
> Hi Folks,
>
> As far as I can tell, md RAID10 is the greatest thing since sliced bread
> - mirroring and striping in one operation (more efficient disk use,
> better performance), avoids the RAID5/6 write hole issue, etc. - I've
> been having very good luck with it on two servers that I run.
>
> The thing is, I'm looking at some scaling and clustering options, and
> can find practically no documentation or case studies or much of any
> information about md RAID10 - which sort of surprises me. I'd think it
> would be more popular and there'd be more comparisons vis-a-vis other
> options.
>
> Anyway... what I'm looking at is trying to create a large storage pool,
> out of 16 drives, spread across 4 servers - essentially trying to create
> a poor man's storage cloud to support a collection of VMs that can be
> migrated for load leveling and failover.
>
> One thought is to expose all the drives via AoE, then combine them into
> one large RAID10 array - but I'm neither sure this is feasible nor how
> it would perform under various loads, failure conditions, etc.
>
> Thoughts, pointers, ....?
there was some bencmarks on our wiki, but it is gone because kernel.org is down.
Any ideas how to remedy the wiki problem?
Best regards
keld
next prev parent reply other threads:[~2011-10-10 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 21:37 md RAID10 questions Miles Fidelman
2011-10-10 22:15 ` keld [this message]
2011-10-10 22:50 ` Miles Fidelman
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=20111010221547.GA30555@www5.open-std.org \
--to=keld@keldix.com \
--cc=linux-raid@vger.kernel.org \
--cc=mfidelman@meetinghouse.net \
/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