From: "Leslie Rhorer" <lrhorer@satx.rr.com>
To: 'Rogier Wolff' <R.E.Wolff@BitWizard.nl>,
'Steven Haigh' <netwiz@crc.id.au>
Cc: linux-raid@vger.kernel.org
Subject: RE: New raid level suggestion.
Date: Sun, 2 Jan 2011 22:33:20 -0600 [thread overview]
Message-ID: <4D.AA.19545.091512D4@cdptpa-omtalb.mail.rr.com> (raw)
In-Reply-To: <20101230094230.GE2986@bitwizard.nl>
> -----Original Message-----
> From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
> owner@vger.kernel.org] On Behalf Of Rogier Wolff
> Sent: Thursday, December 30, 2010 3:43 AM
> To: Steven Haigh
> Cc: Rogier Wolff; linux-raid@vger.kernel.org
> Subject: Re: New raid level suggestion.
>
> 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...
Theree's been quite a bit of back and forth in this thread. I think
it would be best if you could more narrowly define your application.
Exactly what is this app doing? Is it, as has been suggested, a web server?
How many transactions / second is it servicing at peak? How large are the
files? Is there some unusual .cgi script which causes huge amounts of disk
thrashing? You might post the results of iostat.
> Steven, My friend has a server where the drives take up to a third of
> a second to respond.
Respond to what? I have a .cgi script that takes up to 30 seconds
to respond, but it's not because of any lack of array responsiveness. It's
performing all sorts of investigations and calculations. 1/3of a second may
or may not be a terrible delay depending on what is going on, and the delay
may not be as a result of disk I/O.
> When asking for help, everybody pounced on us:
> - NEVER use raid5 for a server doing small-file-io like a mailserver.
> (always use RAID10).
Even a mailserver may not need anything radical in terms of disk
performance, depending on the number of users. Again, you haven't
quantified the number of users the server is tending.
> 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.
A hot spare can certainly mitigate any windshield time, but before
anyone can really determine that RAID5 or RAID5 is not sufficient, one must
specify the actual service parameters.
next prev parent reply other threads:[~2011-01-03 4:33 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
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 ` Leslie Rhorer [this message]
2011-01-04 15:29 ` New raid level suggestion 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=4D.AA.19545.091512D4@cdptpa-omtalb.mail.rr.com \
--to=lrhorer@satx.rr.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=linux-raid@vger.kernel.org \
--cc=netwiz@crc.id.au \
/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).