From: Bill Davidsen <davidsen@tmr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Neil Brown <neilb@suse.de>, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Distributed spares
Date: Tue, 14 Oct 2008 19:20:04 -0400 [thread overview]
Message-ID: <48F52924.7030607@tmr.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0810131810570.16807@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Mon, 13 Oct 2008, Bill Davidsen wrote:
>
>> Over a year ago I mentioned RAID-5e, a RAID-5 with the spare(s)
>> distributed over multiple drives. This has come up again, so I
>> thought I'd just mention why, and what advantages it offers.
>>
>> By spreading the spare over multiple drives the head motion of normal
>> access is spread over one (or several) more drives. This reduces
>> seeks, improves performance, etc. The benefit reduces as the number
>> of drives in the array gets larger, obviously with four drives using
>> only three for normal operation is slower than four, etc. And by
>> using all the drives all the time, the chance of a spare being
>> undetected after going bad is reduced.
>>
>> This becomes important as array drive counts shrink. Lower cost for
>> drives ($100/TB!), and attempts to drop power use by using fewer
>> drives, result in an overall drop in drive count, important in
>> serious applications.
>>
>> All that said, I would really like to bring this up one more time,
>> even if the answer is "no interest."
>>
>> --
>> Bill Davidsen <davidsen@tmr.com>
>> "Woe unto the statesman who makes war without a reason that will still
>> be valid when the war is over..." Otto von Bismark
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> Bill,
>
> Not a bad idea; however, can the same not be acheived (somewhat) by
> performing daily/smart, weekly/long tests on the drive to validate its
> health? I find this to work fairly well on a large scale.
Not really, the performance benefit comes from spreading head motion to
(at least) one more drive. You can get a check on basic functionality
with SMART, but it doesn't beat the drive the way real load does. Add to
that the unfortunate problem that more realistic testing also takes up
i/o bandwidth for non-productive transfers. Better to be doing actual
live data transfers to those drives if you can.
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next prev parent reply other threads:[~2008-10-14 23:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 21:50 Distributed spares Bill Davidsen
2008-10-13 22:11 ` Justin Piszcz
2008-10-13 22:30 ` Billy Crook
2008-10-13 23:29 ` Keld Jørn Simonsen
2008-10-14 10:12 ` Martin K. Petersen
2008-10-14 13:06 ` Keld Jørn Simonsen
2008-10-14 13:20 ` David Lethe
2008-10-14 12:02 ` non-degraded component replacement was " David Greaves
2008-10-14 13:18 ` Billy Crook
2008-10-14 23:20 ` Bill Davidsen [this message]
2008-10-14 10:04 ` Neil Brown
2008-10-16 23:50 ` Bill Davidsen
2008-10-17 4:09 ` David Lethe
2008-10-17 13:46 ` Bill Davidsen
2008-10-20 1:11 ` Neil Brown
2008-10-17 13:09 ` Gabor Gombas
-- strict thread matches above, loose matches on Subject: below --
2008-10-14 13:30 David Lethe
2008-10-14 14:37 ` Keld Jørn Simonsen
2008-10-14 15:18 ` David Lethe
2008-10-14 16:29 ` KELEMEN Peter
2008-10-14 17:16 ` David Lethe
2008-10-14 17:20 ` Mattias Wadenstein
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=48F52924.7030607@tmr.com \
--to=davidsen@tmr.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).