linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dag Nygren <dag@newtech.fi>
To: Chris Murphy <lists@colorremedies.com>
Cc: Phil Turmel <philip@turmel.org>,
	"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 12:23:18 +0200	[thread overview]
Message-ID: <1731429.tcuHV4H7OX@eseries.newtech.fi> (raw)
In-Reply-To: <4ACB5D8F-CC0F-4CF2-96C7-03D05E40C89A@colorremedies.com>

On Friday 24 January 2014 13:54:35 Chris Murphy wrote:
> 
> On Jan 24, 2014, at 12:57 PM, Phil Turmel <philip@turmel.org> wrote:
> 
> > On 01/24/2014 02:32 PM, Chris Murphy wrote:
> >>>> So a URE is either 4096 bits nonrecoverable, or 32768 bits 
> >>>> nonrecoverable, for HDDs. Correct?
> >>> 
> >>> Yes.  Note that the specification is for an *event*, not for a
> >>> specific number of bits lost.  The error rate is not "bits lost per
> >>> bits read", it is "bits lost event per bits read".
> >> 
> >> I don't understand this. You're saying it's a "1 URE event in 10^14
> >> bits read" spec? Not a "1 bit nonrecoverable in 10^14 bits read"
> >> spec?
> >> 
> >> It seems that a nonrecoverable read error rate of 1 in 2 would mean,
> >> 1 bit nonrecoverable per 2 bits read. Same as 512 bits nonrecoverable
> >> per 1024 bits read. Same as 1 sector nonrecoverable per 2 sectors
> >> read.
> > 
> > I don't know what more to say here.  Your "seems" is not.
> 
> Please define "bits lost event" and cite some reference. Google returns exactly ONE hit on that, which is this thread. If we cannot agree on the units, we aren't talking about the same thing, at all, with a commensurately huge misunderstanding of the problem and thus the solution.
> 
> So please to not merely respond to the 2nd paragraph you disagree with. Answer the two questions above that paragraph.
> 
> 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.
> 
> A very simple misunderstanding should have a very simple corrective answer rather than hand waiving and giving up.

I don't see your problem?

1. 1 bit unrecoverable = Data is wrong
2. 1 URE = Data is wrong

They are the same thing! And that will give you the average probablility
of getting a read error?

Best
Dag

  reply	other threads:[~2014-01-25 10:23 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 [this message]
2014-01-25 15:48                                 ` Phil Turmel
2014-01-25 17:44                                   ` Stan Hoeppner
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=1731429.tcuHV4H7OX@eseries.newtech.fi \
    --to=dag@newtech.fi \
    --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).