linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Phil Turmel <philip@turmel.org>, Chris Murphy <lists@colorremedies.com>
Cc: "linux-raid@vger.kernel.org List" <linux-raid@vger.kernel.org>
Subject: Re: Questions about bitrot and RAID 5/6
Date: Sat, 25 Jan 2014 11:44:30 -0600	[thread overview]
Message-ID: <52E3F7FE.6000004@hardwarefreak.com> (raw)
In-Reply-To: <52E3DCE4.4020909@turmel.org>

Hadn't paid attention to this thread til now, as the posts kept piling up.

On 1/25/2014 9:48 AM, Phil Turmel wrote:

> On 01/24/2014 03:54 PM, Chris Murphy wrote:
...
>> If the spec is "1 URE event in 1E14 bits read" that is "1 bit 
>> nonrecoverable in 2.4E10 bits read" for a 512 byte physical sector 
>> drive, and hilariously becomes far worse at "1 bit nonrecoverable in 
>> 3E9 bits read" for 4096 byte physical sector drives.

First, there is no distinction between the terms "unrecoverable read
error" and "non recoverable read error".  They are two terms describing
the same event, the former most often used when referring to what occurs
on the host, the latter in drive.  I'll simply call it a hard read error.

Sector size has no bearing on hard read error probability.  The fact
that a whole sector is failed on a single bit hard error is simply an
artifact of one sector being the smallest request size possible from the
host.

You buy a loaf of bread and find mold on one slice of the 512 in the
package.  The store will only exchange the whole loaf, not just one
slice.  The probability that one slice of the 2.5 million sold that day
might have mold doesn't change with the quantity in each package.

The probability is the same.  The only difference is how much you have
to throw away.


-- 
Stan

  reply	other threads:[~2014-01-25 17:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 20:34 Questions about bitrot and RAID 5/6 Mason Loring Bliss
2014-01-20 21:46 ` NeilBrown
2014-01-20 22:55   ` Peter Grandi
2014-01-21  9:18   ` David Brown
2014-01-21 17:19   ` Mason Loring Bliss
2014-01-22 10:40     ` David Brown
2014-01-23  0:48       ` Chris Murphy
2014-01-23  8:18         ` David Brown
2014-01-23 17:28           ` Chris Murphy
2014-01-23 18:53             ` Phil Turmel
2014-01-23 21:38               ` Chris Murphy
2014-01-24 13:22                 ` Phil Turmel
2014-01-24 16:11                   ` Chris Murphy
2014-01-24 17:03                     ` Phil Turmel
2014-01-24 17:59                       ` Chris Murphy
2014-01-24 18:12                         ` Phil Turmel
2014-01-24 19:32                           ` Chris Murphy
2014-01-24 19:57                             ` Phil Turmel
2014-01-24 20:54                               ` Chris Murphy
2014-01-25 10:23                                 ` Dag Nygren
2014-01-25 15:48                                 ` Phil Turmel
2014-01-25 17:44                                   ` Stan Hoeppner [this message]
2014-01-27  3:34                                     ` Chris Murphy
2014-01-27  7:16                                       ` Mikael Abrahamsson
2014-01-27 18:20                                         ` Chris Murphy
2014-01-30 10:22                                           ` Mikael Abrahamsson
2014-01-30 20:59                                             ` Chris Murphy
2014-01-27  3:20                                   ` Chris Murphy
2014-01-25 17:56                                 ` Wilson Jonathan
2014-01-27  4:07                                   ` Chris Murphy
2014-01-23 22:06               ` David Brown
2014-01-23 22:02             ` David Brown

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=52E3F7FE.6000004@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=philip@turmel.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).