From: Brad Campbell <brad@wasp.net.au>
To: David Lethe <david@santools.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, berk walker <berk@panix.com>,
Bill Davidsen <davidsen@tmr.com>,
Greg Cormier <gcormier@gmail.com>,
linux-raid@vger.kernel.org
Subject: Re: Sleeping hard drives in an array?
Date: Sat, 03 May 2008 19:48:56 +0400 [thread overview]
Message-ID: <481C8968.4050808@wasp.net.au> (raw)
In-Reply-To: <A20315AE59B5C34585629E258D76A97C3359B7@34093-C3-EVS3.exchange.rackspace.com>
David Lethe wrote:
> Then just tweak a few things to take advantage of soft links & the
> ramdisk filesystem for temporary files & scratch space, and such, and
> you get some real performance boosts. It really is an elegant solution
> that many people should consider as general practice. For less than the
> price of a disk drive, put the O/S on SSD, then use md exclusively for
> applications.
> - David @ SANtools ^ com
My storage array boxes are based on Debian. I simply put the *entire* OS into an initramfs that gets
loaded along with the kernel over PXE. That way the entire rotating media is dedicated to the RAID,
and the entire OS runs from RAM. Similar but different.
Yeah, the initramfs is 80MB, but with 1.5GB of ram in each box and all on GB ethernet it really
makes no difference (plus only rebooting about twice a year).
I used to sleep the drives when the array was idle but it interfered with the ability to monitor
them with smartmontools, and also when doing a read it would spin up the disks one by one as each
block request was satisfied (which took forever on the 1st read after spindown). I started to build
some hackery to spin them all up together, then I just gave up and left them rotating.
30,000 hours later I've only had one fail from 30.. (slow grown defects)
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
next prev parent reply other threads:[~2008-05-03 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 15:02 Sleeping hard drives in an array? Greg Cormier
2008-05-01 8:52 ` Mario 'BitKoenig' Holbe
2008-05-01 9:55 ` David Greaves
2008-05-02 21:11 ` Bill Davidsen
2008-05-02 22:11 ` berk walker
2008-05-02 22:44 ` David Lethe
2008-05-03 8:19 ` Michael Tokarev
2008-05-03 15:29 ` David Lethe
2008-05-03 15:48 ` Brad Campbell [this message]
2008-05-05 0:04 ` Bill Davidsen
2008-05-05 0:12 ` Greg Cormier
2008-05-09 13:20 ` Bill Davidsen
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=481C8968.4050808@wasp.net.au \
--to=brad@wasp.net.au \
--cc=berk@panix.com \
--cc=david@santools.com \
--cc=davidsen@tmr.com \
--cc=gcormier@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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).