linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Redeeman <redeeman@metanurb.dk>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Handling mismatch_cnt
Date: Sun, 26 Jul 2009 06:22:34 +0200	[thread overview]
Message-ID: <1248582154.32584.68.camel@localhost> (raw)
In-Reply-To: <4A6A4C73.2070000@eyal.emu.id.au>

On Sat, 2009-07-25 at 10:06 +1000, Eyal Lebedinsky wrote:
> Thanassis Tsiodras wrote:
> > Handling mismatch_cnt<>0
> [trim]
> > Am I missing something? Is MD RAID1 in fact better than what I
> > have understood? Is there an answer that would allow me to use it
>  > without the uncertainty of "russian-roulette" fixes when the
>  > inevitable mismatch_cnt<>0 occurs?
> 
> RAID1 will ensure your data is not lost when one disk completely fails.
> This is a rather common mode of failure. You are protected against this
> catastrophic event but not against (minor? damage of a) sector failure.
> I use RAID for just this benefit.
> 
> Unlike RAID5, RAID6 should be able to do better than a random correction
> (does it?).
Nope
> 
> RAID1 with more than two disks should also do better with voting
> (does it?).
Nope.

Theres a previous thread i started about this, with more details..
> 
> > In other words, is there anything a Linux guy can do besides wait
> > for btrfs or trust a FUSE version of ZFS?
> > 
> > Thanks for any feedback,
> > Thanassis.
> 


      reply	other threads:[~2009-07-26  4:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 16:01 Handling mismatch_cnt Thanassis Tsiodras
2009-07-25  0:06 ` Eyal Lebedinsky
2009-07-26  4:22   ` Redeeman [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=1248582154.32584.68.camel@localhost \
    --to=redeeman@metanurb.dk \
    --cc=eyal@eyal.emu.id.au \
    --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).