From: Phil Turmel <philip@turmel.org>
To: 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 10:48:52 -0500 [thread overview]
Message-ID: <52E3DCE4.4020909@turmel.org> (raw)
In-Reply-To: <4ACB5D8F-CC0F-4CF2-96C7-03D05E40C89A@colorremedies.com>
Hi Chris,
I sat on my reply for a day so I could make sure my response was
suitably professional.
On 01/24/2014 03:54 PM, 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.
I am not trying to define terminology, nor do I intend to. I have been
paraphrasing and rephrasing in an attempt to help you understand the
published terminology. It's hardly surprising that this thread is the
only hit.
As this list is *the* reference for linux raid technology, and is a
reference for raid technology in general, I hope this helps future
googlers understand the issue.
> So please to not merely respond to the 2nd paragraph you disagree
> with. Answer the two questions above that paragraph.
The paired questions simply restated my previous answer with a few
substitutions. I skipped what I presumed was a rhetorical form, and
replied to your commentary in answer to the whole.
> 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.
It is only hilariously far worse in *your* mind.
> A very simple misunderstanding should have a very simple corrective
> answer rather than hand waiving and giving up.
I'm sorry if you think my attempts to teach have been hand-waving. I'm
giving up. I can't help you further.
Regards,
Phil Turmel
next prev parent reply other threads:[~2014-01-25 15:48 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 [this message]
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=52E3DCE4.4020909@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).