From: Bill Davidsen <davidsen@tmr.com>
To: Farkas Levente <lfarkas@lfarkas.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: what superblock to use
Date: Tue, 21 Apr 2009 10:20:17 -0400 [thread overview]
Message-ID: <49EDD621.5090804@tmr.com> (raw)
In-Reply-To: <49EC7B22.8070805@lfarkas.org>
Farkas Levente wrote:
> hi,
> what's the current recommended superblock to use for a newly created
> raid5-6 array with 6 pieces of 1tb disk? by default mdamd use 0.90. is
> it worth to change it to any 1.x format?
> anyway is there any advantage of a raid6 over raid5+1spare disk? afaik
> raid5 will be faster and use less cpu and both case 2 disk can failed.
> thanks in advance.
>
>
Let me be Devil's Advocate. The advantage of raid6 is that it will
survive the failure of two drives at the same time, while a spare must
be rebuilt (a good argument for fast rebuild and let response go to blazes).
The advantage of raid5+S is that with a failure of a single drive you
run your io in recovery mode, and it is slow, while after rebuild on the
spare raid5+S is as fast as ever.
I have been trying some things with raid5e, and as soon as I find a good
primer on using events to kick the recovery off I will be able to report
some sucess with this. My POC uses a script, and works fine if I poll to
detect the disk failure.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
"You are disgraced professional losers. And by the way, give us our money back."
- Representative Earl Pomeroy, Democrat of North Dakota
on the A.I.G. executives who were paid bonuses after a federal bailout.
prev parent reply other threads:[~2009-04-21 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 13:39 what superblock to use Farkas Levente
2009-04-20 14:10 ` Andrew Burgess
2009-04-20 14:17 ` Luca Berra
2009-04-20 19:39 ` Leslie Rhorer
2009-04-20 21:24 ` Luca Berra
2009-04-20 14:17 ` Mario 'BitKoenig' Holbe
2009-04-21 17:31 ` H. Peter Anvin
2009-04-22 16:26 ` Leslie Rhorer
2009-04-21 14:20 ` Bill Davidsen [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=49EDD621.5090804@tmr.com \
--to=davidsen@tmr.com \
--cc=lfarkas@lfarkas.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.