From: Stan Hoeppner <stan@hardwarefreak.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: question about the best suited RAID level/layout
Date: Sat, 06 Jul 2013 03:36:59 -0500 [thread overview]
Message-ID: <51D7D72B.4070401@hardwarefreak.com> (raw)
In-Reply-To: <1373071585.5395.45.camel@fermat.scientia.net>
On 7/5/2013 7:46 PM, Christoph Anton Mitterer wrote:
> On Thu, 2013-07-04 at 20:12 -0500, Stan Hoeppner wrote:
...
> btw: It was interesting to see,... that all 3 different drives (from WD,
> HGST, Seagate)... exported _exactly_ the same amount of space.
You did state these are all enterprise class drives.
>> ... I don't leave
>> 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.
>> 2. HGST is a brand created due to Western Digital's acquisition of
>> Hitachi Data System's disk drive unit.
> Sure... but I think they still use their own technology/firmware... at
> least for now?
For now.
>> The drives are Hitachi's final
>> production units relabeled with a different name and serial number.
>> Three years from now when that HGST drive fails, Western Digital will
>> replace it with a Western Digital produced drive.
> 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?
Got a link?
> 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?
>> IMO the practical disadvantages of using dissimilar drives outweighs the
>> theoretical benefits.
> So... which are the practical disadvantages?
I already stated many of them. You don't seem to be following along
very well.
--
Stan
next prev parent reply other threads:[~2013-07-06 8:36 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 [this message]
2013-07-06 15:04 ` Christoph Anton Mitterer
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=51D7D72B.4070401@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=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 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.