From: Goswin von Brederlow <goswin-v-b@web.de>
To: Ryan Wagoner <rswagoner@gmail.com>
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
Jon@ehardcastle.com, linux-raid@vger.kernel.org
Subject: Re: Raid 5 - not clean and then a failure.
Date: Wed, 26 Aug 2009 22:35:59 +0200 [thread overview]
Message-ID: <87y6p6wbww.fsf@frosties.localdomain> (raw)
In-Reply-To: <7d86ddb90908260714j4ddc6b56w580b511bdcf12491@mail.gmail.com> (Ryan Wagoner's message of "Wed, 26 Aug 2009 10:14:31 -0400")
Ryan Wagoner <rswagoner@gmail.com> writes:
> Wouldn't weekly RAID consistency checks reveal a bad block before you
> had a failure that required the need to do a full resync? It only
> takes 3 hours to resync my 3 x 1TB drives and having a bitmap would
> reduce the performance. I've never had to have a resync in the year
> I've had the array up. I just wonder if the performance drawback is
> worth having the bitmap to save a possible resync once every couple
> years. Or are the RAID consistency checks not reliable enough to
> prevent more errors during a resync?
>
> Ryan
Bitmaps don't protect against disk failures. They help with
intermittent failures, usualy caused by the controler. If you don't
have intermittent failures then bitmaps will only cost you for no
benefit.
MfG
Goswin
prev parent reply other threads:[~2009-08-26 20:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 7:54 Raid 5 - not clean and then a failure Jon Hardcastle
2009-08-25 8:16 ` Robin Hill
2009-08-25 8:40 ` Jon Hardcastle
2009-08-25 9:34 ` Robin Hill
2009-08-25 13:47 ` John Robinson
2009-08-25 14:11 ` Jon Hardcastle
2009-08-26 11:02 ` Jon Hardcastle
2009-08-26 11:18 ` Goswin von Brederlow
2009-08-26 11:29 ` Jon Hardcastle
2009-08-26 12:47 ` John Robinson
2009-08-26 20:34 ` Goswin von Brederlow
2009-08-26 14:14 ` Ryan Wagoner
2009-08-26 14:19 ` Jon Hardcastle
2009-08-26 14:50 ` Robin Hill
2009-08-26 14:33 ` Robin Hill
2009-08-26 20:35 ` Goswin von Brederlow [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=87y6p6wbww.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=Jon@ehardcastle.com \
--cc=linux-raid@vger.kernel.org \
--cc=rswagoner@gmail.com \
/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