linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Max Waterman" <davidmaxwaterman@fastmail.co.uk>
To: David Lethe <david@santools.com>,
	Justin Piszcz <jpiszcz@lucidpixels.com>,
	John Robinson <john.robinson@anonymous.org.uk>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: RE: upgrade advice / Disk drive failure rates - real world
Date: Thu, 18 Dec 2008 22:51:53 +0000	[thread overview]
Message-ID: <1229640713.29109.1290832315@webmail.messagingengine.com> (raw)
In-Reply-To: <A20315AE59B5C34585629E258D76A97C0314BCDA@34093-C3-EVS3.exchange.rackspace.com>


On Thu, 18 Dec 2008 13:14:27 -0600, "David Lethe" <david@santools.com>
said:
snip
>
> So aggregate walk-away
>  - Keep disks in 36-42 degrees C for maximum life up to year 2, where
> they should be run cooler.
>  - New disks are 5x more likely to die in first 3 months with high vs.
> low workload.

I wonder if you can use this fact to make drive which are more likely to
fail later, actually fail sooner.

I'm thinking that I could run my new drives in a fridge for a month or
two or three - if they fail, I'll return them, else I can be more sure
they'll last their expected life and not give me any trouble.

Does that make any sense?

Also, I see people recommending enterprise disks, which makes me think
that those same people have forgotten what the 'I' stands for in 'RAID'.
Of course, 'inexpensive' is relative - probably to one's income and it
seems some people are paid more than others....it almost suggests we
should have another acronym - RADCD - redundant array of dirt cheap
disks. :)

Max.

  reply	other threads:[~2008-12-18 22:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 11:10 upgrade advice Max Waterman
2008-12-16 11:44 ` Justin Piszcz
2008-12-16 11:49   ` Redeeman
2008-12-16 13:07     ` Justin Piszcz
2008-12-16 14:15       ` Redeeman
2008-12-16 15:57         ` Jon Nelson
2008-12-16 16:10           ` Ryan Wagoner
2008-12-16 16:27           ` Redeeman
2008-12-16 23:29           ` Justin Piszcz
2008-12-17  0:08             ` Jon Nelson
2008-12-17  6:59               ` Redeeman
2008-12-17 13:26                 ` Jon Nelson
2008-12-17 14:28                   ` David Lethe
2008-12-17 14:37                     ` Jon Nelson
2008-12-17 15:30                       ` David Lethe
2008-12-18  7:36                         ` Redeeman
2008-12-18 16:37                         ` John Robinson
2008-12-18 16:43                           ` Justin Piszcz
2008-12-18 17:18                             ` John Robinson
2008-12-18 19:14                             ` upgrade advice / Disk drive failure rates - real world David Lethe
2008-12-18 22:51                               ` Max Waterman [this message]
2008-12-19  4:28                                 ` David Lethe
2008-12-17 14:46                     ` upgrade advice Redeeman
2008-12-17 15:38                       ` Martin K. Petersen
2009-01-13  3:00                         ` Bill Davidsen
2009-01-13  4:37                           ` Martin K. Petersen
2008-12-16 13:09     ` Max Waterman
2008-12-16 13:04   ` Max Waterman

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=1229640713.29109.1290832315@webmail.messagingengine.com \
    --to=davidmaxwaterman@fastmail.co.uk \
    --cc=david@santools.com \
    --cc=john.robinson@anonymous.org.uk \
    --cc=jpiszcz@lucidpixels.com \
    --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 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).