From: Stan Hoeppner <stan@hardwarefreak.com>
To: linux-raid@vger.kernel.org
Subject: Re: New raid level suggestion.
Date: Thu, 30 Dec 2010 04:39:41 -0600 [thread overview]
Message-ID: <4D1C616D.8030904@hardwarefreak.com> (raw)
In-Reply-To: <20101230094230.GE2986@bitwizard.nl>
Rogier Wolff put forth on 12/30/2010 3:42 AM:
> On Thu, Dec 30, 2010 at 07:47:10PM +1100, Steven Haigh wrote:
>> Maybe I'm not quite understanding right, however you can easily do RAID6
>> with 4 drives. That will give you two redundant, effectively give you
>> RAID5 if I drive fails, and save buttloads of messing around...
>
> Steven, My friend has a server where the drives take up to a third of
> a second to respond. When asking for help, everybody pounced on us:
> - NEVER use raid5 for a server doing small-file-io like a mailserver.
> (always use RAID10).
>
> So apparently RAID5 (and by extension RAID6) is not an option for some
> systems.
>
> I'm willing to tolerate the RAID4 situation during the time that it
> takes me to replace the drive.
Any RAID scheme that uses parity is less than optimal, and up to
horrible, for heavy random IO loads. As always, this depends on "how
heavy" the load is. For up to a few hundred constant IOPS you can get
away with parity RAID schemes. If you need a few thousand or many
thousand IOPS, better stay away from parity RAID.
This includes RAID 3 and 4. Both of these are now defunct because using
a dedicated disk for storing parity information for an array yields the
same or very slightly higher reliability than using a single disk (I
don't have the equation in front me to give exact probability of
failure). Regardless, if the RAID 3/4 parity disk fails you lose the array.
If your friend's web server isn't going to see a ton of traffic, why
does he need anything beyond a 2 way mirror with a spare? Paraniod? Do
a 3 way mirror. A mirrored pair of 10k RPM SATA drives should be more
than sufficient for most webservers, which typically gain their
performance from lots of buffer cache, not from fast disks.
If would help if we knew more about the specific web app he's hosting,
its IO patterns, and anticipated load once in production. Unless he's
got a super complex (read inefficient) cgi/database back end my
recommendation of a pair of mirrored drives, stands. 7.2k would
probably be fine, 10k gives a little wiggle room if you underestimate
your load target, or the app turns out to be even less efficient that
anticipated.
--
Stan
next prev parent reply other threads:[~2010-12-30 10:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 8:23 New raid level suggestion Rogier Wolff
2010-12-30 8:47 ` Steven Haigh
2010-12-30 9:42 ` Rogier Wolff
2010-12-30 10:39 ` Stan Hoeppner [this message]
2010-12-30 11:58 ` John Robinson
2010-12-30 13:11 ` Stan Hoeppner
2010-12-30 18:10 ` John Robinson
2010-12-31 10:23 ` Stan Hoeppner
2010-12-30 23:20 ` Why won't mdadm start several RAIDs that appear to be fine? Jim Schatzman
2010-12-31 1:08 ` Neil Brown
2010-12-31 3:38 ` Why won't mdadm start several RAIDs that appear to be fine? Info from "mdadm -A --verbose" Jim Schatzman
2010-12-31 3:51 ` Why won't mdadm start several RAIDs that appear to be fine? SOLVED! Jim Schatzman
2011-01-03 4:33 ` New raid level suggestion Leslie Rhorer
2011-01-04 15:29 ` Rogier Wolff
2010-12-30 10:01 ` Neil Brown
2010-12-30 14:24 ` Ryan Wagoner
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=4D1C616D.8030904@hardwarefreak.com \
--to=stan@hardwarefreak.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).