All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: NeilBrown <neilb@suse.de>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
	linux-raid@vger.kernel.org, g.danti@assyoma.it
Subject: Re: On URE and RAID rebuild - again!
Date: Tue, 05 Aug 2014 08:52:01 +0200	[thread overview]
Message-ID: <53E07F11.5050103@assyoma.it> (raw)
In-Reply-To: <20140805092951.7d8f8e6d@notabene.brown>



On 05/08/2014 01:29, NeilBrown wrote:
> On Tue, 05 Aug 2014 00:44:04 +0200 Gionatan Danti <g.danti@assyoma.it> wrote:
>
>
> Probabilities are often calculated by examining a statistical record - the
> two concepts are not separate.
> There is probably some theoretical analysis, some statistical analysis, some
> marketing and maybe even some actuarial analysis that goes in to the quoted
> figure.  I remember when CPU speed was measured in "MIPS".
> This stood for
>     Meaningless Indicators of Performance for Salesmen
>
> URE rates numbers are probably equally trustworthy.
>
> The probability number doesn't tell you much at all about your drive.
> Your drive probably works much better than the quoted rate, but could be much
> worse.
> The quoted number might say something useful about a collection of 10,000
> drives, but if you can afford those, you can probably afford to competent
> statistician to explain the details too.
>
>
>
> I'm not an electro-magnetic engineer, but I would guess that UREs are caused
> by some combination of:
>   - irregularities in the physical media
>   - imperfections in positioning of the write head
>   - fluctuations in temperature and pressure which could
>     affect precise performance of resistors and capacitors etc.
>
> and probably various quantum effects that I know nothing about.
>
> Maybe most UREs come from a spec of dust that was in the wrong place at the
> wrong time.
>
> If think a better summary would be:
>    in normal conditions and typical loads, a collection of 10^14 drives will
>    exhibit errors somewhere in the collection on a regular basis.
>
>
> NeilBrown
>

VERY informative post. Thank you Neil.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

  reply	other threads:[~2014-08-05  6:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30  8:29 On URE and RAID rebuild - again! Gionatan Danti
2014-07-30 11:13 ` Mikael Abrahamsson
2014-07-30 13:05   ` Gionatan Danti
2014-07-30 21:31     ` NeilBrown
2014-07-31  7:16       ` Gionatan Danti
2014-08-02 16:21         ` Gionatan Danti
2014-08-03  3:48           ` NeilBrown
2014-08-04  7:02             ` Mikael Abrahamsson
2014-08-04  7:13               ` NeilBrown
2014-08-04 13:27             ` Gionatan Danti
2014-08-04 18:40               ` Mikael Abrahamsson
2014-08-04 22:44                 ` Gionatan Danti
2014-08-04 23:29                   ` NeilBrown
2014-08-05  6:52                     ` Gionatan Danti [this message]
2014-08-05 19:01                   ` Piergiorgio Sartor
2014-08-05 19:42                     ` Gionatan Danti
2014-08-06 17:05                       ` Chris Murphy
2014-08-06 16:34                   ` Chris Murphy

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=53E07F11.5050103@assyoma.it \
    --to=g.danti@assyoma.it \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=swmike@swm.pp.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.