From: Russell Coker <bofh@coker.com.au>
To: linux-lvm@sistina.com, zoo1@corecomm.net
Subject: Re: [linux-lvm] hard drive shock tolerance
Date: Sat, 13 Jan 2001 05:51:57 +1100 [thread overview]
Message-ID: <0101130551570E.27982@lyta> (raw)
In-Reply-To: <20010110195439.A11865@bar.nowhere>
On Thursday 11 January 2001 11:54, zoo1@corecomm.net wrote:
> On Wed, Jan 10, 2001 at 01:39:13AM +1100, Russell Coker wrote:
> >My "gut feeling" is that drives are more susceptible to damage now. I
> > know of cases of older 3600rpm drives being dropped, being hit by a car
> > while operating (car entered building through the wall of the computer
> > room), and suffering numerous other mechanically damaging events without
> > data loss. I belive that modern 10K rpm drives are not as solid.
>
> hit by a car? you're serious? i can't even imagine a modern disk
An idiot in the drive of the next house mistook the accelerator pedal in an
automatic car for the brake, she kept pressing it harder when the car didn't
stop.
The car entered through a solid brick wall that the computer had been in
front of. The computer ended up on the floor at the far side of the room (~4
meters away).
The car was stopped from going further through the house by rubble which
supported much of the weight of the car and prevented the rear wheels from
gaining traction. For some time the car was burning rubber on the spot...
> >Also drives are more susceptible to heat problems. 3600rpm drives
> >could operate with all their air-holes blocked and while surrounded by
> >other hard drives without problems. You can't stack two new 10K rpm
> >drives without good fans.
>
> i'll take your word for it. myself, i never see drives like that in
> PCs, just in workstations and RAID arrays with more than adequate
> cooling; but then again, i don't see PCs much these days anymore.
Most hardware work I do is with PCs. When dealing with rack mounted server
equipment I generally do the software and someone else deals with the
hardware.
Given a choice I prefer hard drives with lower rotational speeds because of
the lesser heat production. Read the spec sheets and you'll see that as a
general rule 10K rpm drives use twice as much power as 7200 rpm drives, twice
the power == twice the heat!
The really worrying thing about heat death is that it's one of the few ways
that I could imagine two hard drives in a mirrored set dieing before I get a
chance to replace one!
--
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page
next prev parent reply other threads:[~2001-01-12 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 23:54 [linux-lvm] any way to locate vg's on, say, /etc? Steven Lembark
2001-01-07 7:27 ` Russell Coker
2001-01-07 19:47 ` Joe Thornber
[not found] ` <0101090031381K.05036@lyta>
[not found] ` <3A5AAF8C.305C862D@wrkhors.com>
2001-01-09 14:39 ` Russell Coker
2001-01-11 0:54 ` [linux-lvm] hard drive shock tolerance zoo1
2001-01-12 18:51 ` Russell Coker [this message]
2001-01-12 21:41 ` Scott Laird
2001-01-15 4:37 ` Russell Coker
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=0101130551570E.27982@lyta \
--to=bofh@coker.com.au \
--cc=linux-lvm@sistina.com \
--cc=zoo1@corecomm.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 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.