From: Brad Campbell <brad@wasp.net.au>
To: bart@ardistech.com
Cc: Mike Dresser <mdresser_l@windsormachine.com>, linux-raid@vger.kernel.org
Subject: Re: Ok to go ahead with this setup?
Date: Wed, 28 Jun 2006 10:45:01 +0400 [thread overview]
Message-ID: <44A2256D.7070604@wasp.net.au> (raw)
In-Reply-To: <44A2204D.D21130B7@ardistech.com>
bart@ardistech.com wrote:
> Mike Dresser wrote:
>> On Fri, 23 Jun 2006, Molle Bestefich wrote:
>>
>>> Christian Pernegger wrote:
>>>> Anything specific wrong with the Maxtors?
>>> I'd watch out regarding the Western Digital disks, apparently they
>>> have a bad habit of turning themselves off when used in RAID mode, for
>>> some reason:
>>> http://thread.gmane.org/gmane.linux.kernel.device-mapper.devel/1980/
>> The MaxLine III's (7V300F0) with VA111630/670 firmware currently timeout
>> on a weekly or less basis.. I'm still testing VA111680 on a 15x300 gig
>> array
>>
> We also see similar problem on Maxtor 6V250F0 drives: they 'crash' randomly at
> a weeks timescale. Only way to get them back is by power cycling. Tried both
> SuperMicro SATA card (Marvell chip) and Promise Fastrak, firmware updates from
> Maxtor did not fix it yet. We were already forced to exchange all drives at
> a customer because he does not want to use Maxtor's anymore. Neither do we :(
Whereas I have 28 7Y250M0 drives sitting in a couple of arrays here that have behaved perfectly
(aside from some grown defects) for over 18000 hours so far. They are *all* sitting on Promise
SATA150TX4 cards on 2.6 kernels.
I'm looking at another server and another 15 drives at the moment, and it's Maxtors I'm looking at.
Everyone has different experience. I would not touch Seagate with a 10 foot pole (blew up way too
many logic boards when I was using them), and I got bitten *badly* by the WD firmware issue with
RAID (firmware upgrade fixed that, but can't replace the data I lost when 3 of them failed at the
same time and the array got corrupted).
Having said that, it was MaxLineIII 300G drives I was looking at, so perhaps I'll wait a little
longer and hear some more stories before I drop $$ on 15 of them.
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:[~2006-06-28 6:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 17:08 Ok to go ahead with this setup? Christian Pernegger
2006-06-22 18:04 ` Molle Bestefich
2006-06-22 18:38 ` H. Peter Anvin
2006-06-22 19:50 ` Christian Pernegger
2006-06-22 22:11 ` Molle Bestefich
2006-06-23 2:44 ` H. Peter Anvin
2006-06-23 3:27 ` Bill Davidsen
2006-06-23 6:45 ` Ricky Beam
2006-06-28 2:42 ` Mike Dresser
2006-06-28 6:23 ` bart
2006-06-28 6:45 ` Brad Campbell [this message]
2006-06-28 10:18 ` Justin Piszcz
2006-06-28 15:23 ` Mike Dresser
2006-06-28 7:25 ` Christian Pernegger
2006-06-28 7:58 ` bart
2006-06-28 8:19 ` Drive issues in RAID vs. not-RAID Gordon Henderson
2006-06-29 3:51 ` Neil Brown
2006-06-23 3:25 ` Ok to go ahead with this setup? Bill Davidsen
2006-06-28 12:02 ` Christian Pernegger
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=44A2256D.7070604@wasp.net.au \
--to=brad@wasp.net.au \
--cc=bart@ardistech.com \
--cc=linux-raid@vger.kernel.org \
--cc=mdresser_l@windsormachine.com \
/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.