From: Max Waterman <davidmaxwaterman+gmane@fastmail.co.uk>
To: linux-raid@vger.kernel.org
Subject: Re: First RAID Setup
Date: Fri, 16 Dec 2005 09:51:10 +0800 [thread overview]
Message-ID: <dnt6if$q2o$1@sea.gmane.org> (raw)
In-Reply-To: <43A1E0CE.7090805@medien.uni-weimar.de>
Tobias Hofmann 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?
Just so I am clear on this : while RAID5 consumes a disk's worth of
space for parity, resulting in n-1 disk's worth of space available for
storage, RAID6 consumes two disk's worth of space for two parities,
resulting in n-2 disk's worth of space available for storage.
Is that correct?
>
>
> Me too. ;) So, with holidays ahead, two questions (as I might tackle
> that soon and have not found it mentioned):
I would guess one reason might be that you only have 3 disks - ok
(minimum) for RAID5, but not for RAID6 (minimum is 4?)?
>
> - How would one "switch" from the latter to the former? Is there
> something like "grow_to_RAID_6"?
I'd like to know this too. RAID6 sounds ideal for my array (8 disks -
currently 6 RAID5 + 2 spares; one is currently at the cleaners) - I
could even have an extra disk's worth of space, I think.
> - Does RAID6 have disadvantages wrt write speed?
...and what about rebuilding speed? Does it have to read and process
twice as much parity data?.
Perhaps it is faster for reading (data can be spread across another disk
[which would be empty in the RAID5+spare config]).
Max.
>
> TIA for any comments,
>
> greets, tobi... :)
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2005-12-16 1:51 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 [this message]
2005-12-16 8:01 ` Tobias Hofmann
2005-12-16 1:53 ` Neil Brown
2005-12-16 8:08 ` Tobias Hofmann
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='dnt6if$q2o$1@sea.gmane.org' \
--to=davidmaxwaterman+gmane@fastmail.co.uk \
--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).