All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Kyle Bader <kyle@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Reliability models
Date: Wed, 15 Jan 2014 00:44:13 +0100	[thread overview]
Message-ID: <52D5CBCD.5000608@dachary.org> (raw)
In-Reply-To: <CAHxYaFP2Au1A61B=v3BZLhjdYEXDuO5C_0CLZy3O52TNy=asDg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

Crystal clear, thanks !

On 13/01/2014 18:25, Kyle Bader wrote:
> Hi Loic,
> 
>> IIRC you figured out how to use https://github.com/ceph/ceph-tools/tree/master/models . Do you happen to have some kind of HOWTO or even the list of commands you've used to get me started ?
> 
> git clone ...ceph-tools
> cd ceph-tools/models/reliability
> ./main.py -g
> 
> At this point a graphical form should pop up and most of it should be
> straight forward. NRE rate is non recoverable read errors, the NRE
> model determines how an array/disk responds to a non recoverable read
> error event. I tend to be on the conservative end having seen my share
> of RAID horror shows so I set the NRE model to "fail". The other
> gotcha is most disk manufacturers use MTBF or AFR while the
> reliability modeling tool requests FITS. The formula you will need is:
> 
> MTBF = 1,000,000,000 x 1/FIT. [1]
> 
> Stripe length is the number of RADOS objects that are require to store
> a blob of data, ie all RADOS objects that compose a RBD volume. Since
> this code was written a while ago there is no code to support modeling
> erasure coded objects. If you have any questions, let me know!
> 
> [1] http://en.wikipedia.org/wiki/Failure_rate#Units
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2014-01-14 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13  8:48 Reliability models Loic Dachary
2014-01-13 17:25 ` Kyle Bader
2014-01-14 23:44   ` Loic Dachary [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=52D5CBCD.5000608@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=kyle@inktank.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 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.