From: Giovanni Tessore <giotex@texsoft.it>
To: linux-raid@vger.kernel.org
Subject: Re: recommending RAID6 over RAID5 when doing mdadm --create
Date: Tue, 12 Nov 2013 08:12:37 +0100 [thread overview]
Message-ID: <5281D4E5.6080304@texsoft.it> (raw)
In-Reply-To: <20131112135243.285834fa@notabene.brown>
On 11/12/2013 03:52 AM, NeilBrown wrote:
> On Mon, 11 Nov 2013 02:56:37 -0600 Stan Hoeppner <stan@hardwarefreak.com>
> wrote:
>
>> On 11/11/2013 1:44 AM, Mikael Abrahamsson wrote:
>>
>>> I believe this has been discussed before, but I would like to bring it
>>> up again.
>>>
>>> I would like to see mdadm recommend RAID6 over RAID6 when using
>>> component drives that are 500GB or larger and ask if the user is really
>>> sure about using RAID5, plus a pointer to a webpage on the wiki
>>> informing the user about the trouble with RAID5 on large volumes with
>>> consumer or prosumer drives.
>>>
>>> I am willing to contribute text to the webpage being pointed to.
>> Wikis change to regularly, too easily. Networks can be down at times,
>> often the worst times. See Murphy's Law.
>>
>> It would be better to put this information in mdadm(8) and refer the
>> user there.
>>
> .. or in md(4) maybe.
>
> If anyone wants to run with this and send me a patch (for code and
> documentation) I would be very likely to apply it.
>
> NeilBrown
That issue (RAID5 going fully down during resync of degraded array if
read errors occur) hasn't been addressed by the badblocks log feature
available in later kernels and mdadm ?
Yet, it is not clear to me if the fetaure is fully implemented and
operational.
Regards
Giovanni
prev parent reply other threads:[~2013-11-12 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 7:44 recommending RAID6 over RAID5 when doing mdadm --create Mikael Abrahamsson
2013-11-11 8:24 ` Tommy Apel
2013-11-11 8:56 ` Stan Hoeppner
2013-11-11 9:37 ` Tommy Apel
2013-11-11 11:37 ` joystick
2013-11-12 2:52 ` NeilBrown
2013-11-12 7:12 ` Giovanni Tessore [this message]
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=5281D4E5.6080304@texsoft.it \
--to=giotex@texsoft.it \
--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).