All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark Klarzynski" <mark.k@computer-design.co.uk>
To: linux-raid@vger.kernel.org
Subject: RE: Good news / bad news - The joys of RAID
Date: Sat, 20 Nov 2004 20:03:42 -0000	[thread overview]
Message-ID: <037501c4cf3c$11c8dba0$030a0a0a@musicroom> (raw)
In-Reply-To: <200411201937.iAKJbwN17977@www.watkins-home.com>

MTBF is statistic based upon the expected 'use' of the drive and the
replacement of the drive after its end of life (3-5 years)...

It's extremely complex and boring but the figure is only relative if the
drive is being used within an environment that matches those of the
calculations.

SATA / IDE drives have an MTBF similar to that of SCSI / Fibre. But this
is based upon their expected use... i.e. SCSI used to be [power on hours
= 24hr] [use = 8 hours].. whilst SATA used to be [power on = 8 hours]
and [use = 20 mins].

Regardless of what some people clam (usually those that only sell sata
based raids), the drives are not constructed the same in any way.

SATA's fail more within a raid environment (probably around 10:1)
because of the heavy use and also because they are not as intelligent...
therefore when they do not respond we have no way of interrogating them
or resetting them, whilst with scsi we do both. This means that a raid
controller / driver has no option to but simply fail the drive.

Maxtor lead the way in capacity and also reliability... I personal had
to recall countless earlier IBMs and replace them with maxtor.  But the
new generation of IBM's (Hitachi) have got it together.

So - I guess you are all right :) 




  reply	other threads:[~2004-11-20 20:03 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19 21:06 Good news / bad news - The joys of RAID Robin Bowes
2004-11-19 21:28 ` Guy
2004-11-20 18:42   ` Mark Hahn
2004-11-20 19:37     ` Guy
2004-11-20 20:03       ` Mark Klarzynski [this message]
2004-11-20 22:17         ` Mark Hahn
2004-11-20 23:09           ` Guy
2004-12-02 16:47           ` TJ
2004-12-02 17:29             ` Stephen C Woods
2004-12-03  3:37             ` Mark Hahn
2004-12-03  4:16               ` Guy
2004-12-03  4:46                 ` Alvin Oga
2004-12-03  5:24                 ` Richard Scobie
2004-12-03  5:40                   ` Konstantin Olchanski
2004-12-09  0:17             ` H. Peter Anvin
2004-11-20 23:30       ` Mark Hahn
2004-11-20 19:40     ` David Greaves
2004-11-21  4:33       ` Guy
2004-11-21  1:01     ` berk walker
2004-11-23 19:10     ` H. Peter Anvin
2004-11-23 20:03       ` Guy
2004-11-23 21:18         ` Mark Hahn
2004-11-23 23:02           ` Robin Bowes
2004-11-24  0:33             ` Guy
2004-11-24  1:45           ` berk walker
2004-11-24  2:00             ` H. Peter Anvin
2004-11-24  8:01               ` Good news / bad news - The joys of hardware Guy
2004-11-24  8:57                 ` Robin Bowes
2004-11-19 21:42 ` Good news / bad news - The joys of RAID Guy
2004-11-28 13:15   ` Robin Bowes
2004-11-30  2:05     ` Neil Brown
2004-12-01  3:34       ` Doug Ledford
2004-12-01 11:50         ` Robin Bowes
2004-11-19 21:58 ` Gordon Henderson
     [not found] <037401c4cf3b$ee75bc90$030a0a0a@musicroom>
2004-11-21  4:33 ` Guy
2004-11-22 14:13   ` Yu Chen
2004-11-22 14:34     ` Gordon Henderson
2004-11-22 17:51       ` Guy
2004-11-22 23:26         ` Gordon Henderson
2004-11-22 23:48           ` Guy
2004-11-23  0:09             ` Måns Rullgård
2004-11-23 15:33             ` Gordon Henderson
2004-11-23  0:17     ` berk walker
2004-11-23  9:24       ` Robin Bowes
2004-11-23 12:31         ` Bob Hillegas
2004-11-23 13:00           ` berk walker
     [not found] <Pine.LNX.4.44.0411201655400.19120-100000@coffee.psychology.mcmaster.ca>
2004-11-21 21:28 ` Mark Klarzynski
2004-11-21 21:58   ` Mark Hahn
2004-11-22  6:29   ` Mikael Abrahamsson
     [not found] <04Nov26.172857est.30052@gpu.utcc.utoronto.ca>
2004-11-26 22:41 ` Robin Bowes

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='037501c4cf3c$11c8dba0$030a0a0a@musicroom' \
    --to=mark.k@computer-design.co.uk \
    --cc=linux-raid@vger.kernel.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 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.