From: Tobias Hofmann <tobias.hofmann@medien.uni-weimar.de>
To: Neil Brown <neilb@suse.de>
Cc: Brad Campbell <brad@wasp.net.au>,
"Callahan, Tom" <CallahanT@tessco.com>,
'Andargor The Wise' <andargor@yahoo.com>,
linux-raid@vger.kernel.org
Subject: Re: First RAID Setup
Date: Fri, 16 Dec 2005 09:08:10 +0100 [thread overview]
Message-ID: <43A275EA.9020104@medien.uni-weimar.de> (raw)
In-Reply-To: <17314.7734.707554.88728@cse.unsw.edu.au>
On 16.12.2005 02:53, Neil Brown wrote:
> On Thursday December 15, tobias.hofmann@medien.uni-weimar.de wrote:
>
>><delurk>
>>
>>On 15.12.2005 21:46, Brad Campbell wrote:
>>
>>>Callahan, Tom wrote:
>>>
>>>
>>>>It is always wise to build in a spare however, that being said about all
>>>>raid levels. In your configuration, if a disk fails in your RAID5, your
>>>>array will go down. RAID5 is usually 3+ disks, with a mirror. So you
>>>>should
>>>>have 3 disks at minimum, and then a 4th as a spare.
>>>
>>>/me wonders in the days of reliable RAID-6 why we use RAID-5 + spare?
>>
>>Me too. ;) So, with holidays ahead, two questions (as I might tackle
>>that soon and have not found it mentioned):
>>
>>- How would one "switch" from the latter to the former? Is there
>>something like "grow_to_RAID_6"?
>
>
> No... at least not yet....
Hm. :) Around here, it is pretty much Christmas time, with all the
"wishing" going on - hint, hint? ;)
>>- Does RAID6 have disadvantages wrt write speed?
>
> Probably. I haven't done any measurements myself, but from a
> theoretical standpoint, you would expect raid6 to impose more CPU load
> (though that may not be noticeable) and as raid6 need to see the whole
> stripe to update the P and Q blocks (it cannot do a subtract old, add
> new update) there could well be more IO happening, particularly on
> large arrays (>5 devices).
That,s about the line of thinking I was considering. I,ll see, if I
tackle this over the holidays, to do some tests...
> Of course, whether this caused noticeable reduction in throughput and
> latency would be very workload-dependant.
My scenarios here @home will probably not be very relevant to what one
would like to know in a production environment - whatever that is... :)
Thanks for the input, Neil,
greets, tobi... :)
next prev parent reply other threads:[~2005-12-16 8:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 20:02 First RAID Setup Callahan, Tom
2005-12-15 20:22 ` Andargor The Wise
2005-12-15 20:46 ` Brad Campbell
2005-12-15 21:31 ` Tobias Hofmann
2005-12-16 1:51 ` Max Waterman
2005-12-16 8:01 ` Tobias Hofmann
2005-12-16 1:53 ` Neil Brown
2005-12-16 8:08 ` Tobias Hofmann [this message]
2005-12-19 1:02 ` Neil Brown
2005-12-19 9:03 ` Max Waterman
2005-12-16 8:42 ` Gordon Henderson
2005-12-22 14:20 ` Bill Davidsen
2005-12-22 14:24 ` Mattias Wadenstein
-- strict thread matches above, loose matches on Subject: below --
2005-12-22 17:03 Andrew Burgess
2005-12-15 21:46 Callahan, Tom
2005-12-15 20:37 Callahan, Tom
2005-12-17 0:00 ` Andargor The Wise
2005-12-17 2:01 ` Andargor The Wise
2005-12-18 22:08 ` Andargor The Wise
2005-12-22 14:27 ` Bill Davidsen
2005-12-22 15:00 ` Andargor The Wise
2005-12-15 19:35 Callahan, Tom
2005-12-15 19:44 ` Andargor The Wise
2005-12-22 14:00 ` Bill Davidsen
2005-12-15 19:09 Andargor The Wise
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=43A275EA.9020104@medien.uni-weimar.de \
--to=tobias.hofmann@medien.uni-weimar.de \
--cc=CallahanT@tessco.com \
--cc=andargor@yahoo.com \
--cc=brad@wasp.net.au \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).