From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-raid@vger.kernel.org
Subject: Re: question about the best suited RAID level/layout
Date: Sat, 06 Jul 2013 17:04:11 +0200 [thread overview]
Message-ID: <1373123051.5217.19.camel@fermat.scientia.net> (raw)
In-Reply-To: <51D7D72B.4070401@hardwarefreak.com>
[-- Attachment #1: Type: text/plain, Size: 2011 bytes --]
On Sat, 2013-07-06 at 03:36 -0500, Stan Hoeppner wrote:
> >> hot/warm/cold spares in the chassis.
> >> This simply degrades performance.
> > Why should it? If the spare is unused?
> The answer is rather obvious. If spares are in the chassis one has
> fewer active array spindles.
Sorry... still don't get it...
When you have another drive in the chassis... which is not actively used
by the RAID, but just waiting as a hot spare for a failing device and
rebuild becoming necessary...
Apart from power consumption and more heat... how should that affect the
read/write performance of the RAID?
> > Sure about that? Wasn't there some agreement that HGST belongs to WD but
> > produces independently...?
>
> That wouldn't make sense for either party. Where did you read this?
I vaguely remember this being part for some anti trust obligations...
> Got a link?
The only thing I've found right now was:
https://en.wikipedia.org/wiki/HGST#History
"It was agreed that WD would operate with WD Technologies and HGST as
wholly owned subsidiaries and they would compete in the marketplace with
separate brands and product lines."
But the next sentence about Toshiba may indicate that HGST stops 3.5"
business?!
> > and Toshiba got something from the
> > WD/HGST trade and already announced a 3.5" enterprise disk out of that.
> Toshiba has been producing 3.5" enterprise drives for years. Got a link
> showing that Toshiba received technology from the WD/Hitachi acquisition?
Again, see Wikipedia.
> I already stated many of them. You don't seem to be following along
> very well.
Well you only named one may need to use partitions (which I do not see
why this should be a disadvantage)... and that in few years... there
might be only some vendors left and (by then) the idea wouldn't work
anymore; but even if that would happen, that's still no reason for not
doing it now?
Anything else I've missed or didn't understand as a disadvantage?
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5113 bytes --]
next prev parent reply other threads:[~2013-07-06 15:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 18:17 question about the best suited RAID level/layout Christoph Anton Mitterer
2013-07-04 21:43 ` Phil Turmel
2013-07-04 22:58 ` Christoph Anton Mitterer
2013-07-05 1:07 ` Brad Campbell
2013-07-06 0:36 ` Christoph Anton Mitterer
2013-07-06 5:29 ` Brad Campbell
2013-07-06 14:49 ` Christoph Anton Mitterer
2013-07-07 6:36 ` Brad Campbell
2013-07-06 7:40 ` Piergiorgio Sartor
2013-07-06 14:52 ` Christoph Anton Mitterer
2013-07-05 1:12 ` Stan Hoeppner
2013-07-06 0:46 ` Christoph Anton Mitterer
2013-07-06 8:36 ` Stan Hoeppner
2013-07-06 15:04 ` Christoph Anton Mitterer [this message]
2013-07-06 15:41 ` Matt Garman
2013-07-07 14:08 ` David Brown
2013-07-07 16:45 ` Stan Hoeppner
2013-07-07 17:26 ` Christoph Anton Mitterer
2013-07-09 15:50 ` Stan Hoeppner
2013-07-05 13:36 ` Phil Turmel
2013-07-06 1:11 ` Christoph Anton Mitterer
2013-07-06 2:19 ` Phil Turmel
2013-07-06 17:55 ` Christoph Anton Mitterer
2013-07-07 12:46 ` Bernd Schubert
2013-07-07 17:39 ` Christoph Anton Mitterer
2013-07-05 11:10 ` David Brown
2013-07-06 0:55 ` Christoph Anton Mitterer
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=1373123051.5217.19.camel@fermat.scientia.net \
--to=calestyo@scientia.net \
--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).