From: Konstantin Olchanski <olchansk@triumf.ca>
To: David Liontooth <liontooth@cogweb.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Hard drive lifetime: wear from spinning up or rebooting vs running
Date: Sun, 5 Feb 2006 19:57:59 -0800 [thread overview]
Message-ID: <20060206035759.GB25631@sam.triumf.ca> (raw)
In-Reply-To: <43E68D62.4080704@cogweb.net>
On Sun, Feb 05, 2006 at 03:42:26PM -0800, David Liontooth wrote:
> In designing an archival system, we're trying to find data on when it
> pays to power or spin the drives down versus keeping them running.
>
> Temperature obviously matters -- a linear approximation might look like this,
> Lifetime = 60 - 12 [(t-40)/2.5]
I would expect an exponential rather than linear formula (linear formula yelds
negative life times). L = ... exp(-T) or L = ... exp(1/kT)
> Does anyone have an actual formula?
I doubt it, because it requires measuring lifetimes, which takes
years, by which time the data are useless because the disks you used
are obsolete.
> Or are different components stressed in a running drive versus one that
> is spinning up, so it's not possible to translate the cost of one into
> the currency of the other?
I would expect that spinning-up a drive is very stressful and is likely
to kill the drive [spindle motor power electronics]. In my experience
disk die about evenly from 3 causes: no spinning (dead spindle motor
power electronics), heads do not move (dead head motor power
electronics), or spontaneusly developing bad sectors (disk platter
contamination?).
Hmm... NASA-type people may have data for life times of power electronics,
at least the shape of the temperature dependance (linear or exp or ???).
--
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
next prev parent reply other threads:[~2006-02-06 3:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 5:59 RAID 16? David Liontooth
2006-02-02 6:03 ` Neil Brown
2006-02-02 8:34 ` Gordon Henderson
2006-02-02 16:17 ` Matthias Urlichs
2006-02-02 16:28 ` Mattias Wadenstein
2006-02-02 16:54 ` Gordon Henderson
2006-02-02 20:24 ` Matthias Urlichs
2006-02-02 21:18 ` J. Ryan Earl
2006-02-02 21:29 ` Andy Smith
2006-02-02 22:38 ` Konstantin Olchanski
2006-02-03 2:31 ` Ross Vandegrift
2006-02-03 2:54 ` Bill Davidsen
2006-02-02 18:42 ` Mario 'BitKoenig' Holbe
2006-02-02 20:34 ` Matthias Urlichs
2006-02-03 0:20 ` Guy
2006-02-03 0:59 ` David Liontooth
2006-02-02 16:44 ` Mr. James W. Laferriere
2006-02-03 9:08 ` Lars Marowsky-Bree
2006-02-03 2:32 ` Bill Davidsen
2006-02-05 23:42 ` Hard drive lifetime: wear from spinning up or rebooting vs running David Liontooth
2006-02-06 3:57 ` Konstantin Olchanski [this message]
2006-02-06 5:25 ` Patrik Jonsson
2006-02-06 4:35 ` Richard Scobie
2006-02-06 10:09 ` Mattias Wadenstein
2006-02-06 16:45 ` David Liontooth
2006-02-06 17:12 ` Francois Barre
2006-02-07 8:44 ` Hans Kristian Rosbach
2006-02-07 19:18 ` Neil Bortnak
2006-02-06 19:22 ` Brad Dameron
2006-02-06 21:15 ` Dan Stromberg
2009-09-20 19:44 ` RAID 16? Matthias Urlichs
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=20060206035759.GB25631@sam.triumf.ca \
--to=olchansk@triumf.ca \
--cc=linux-raid@vger.kernel.org \
--cc=liontooth@cogweb.net \
/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).