Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Miles Fidelman <mfidelman@meetinghouse.net>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: md RAID10 questions
Date: Mon, 10 Oct 2011 17:37:03 -0400	[thread overview]
Message-ID: <4E93657F.1090500@meetinghouse.net> (raw)

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, ....?

Thanks,

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In<fnord>  practice, there is.   .... Yogi Berra



             reply	other threads:[~2011-10-10 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 21:37 Miles Fidelman [this message]
2011-10-10 22:15 ` md RAID10 questions keld
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=4E93657F.1090500@meetinghouse.net \
    --to=mfidelman@meetinghouse.net \
    --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