linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: Guy <bugzilla@watkins-home.com>
Cc: 'Jim Paris' <jim@jtan.com>,
	comsatcat@earthlink.net, linux-raid@vger.kernel.org
Subject: Re: Busted disks caused healthy ones to fail
Date: Wed, 15 Dec 2004 09:22:12 +0400	[thread overview]
Message-ID: <41BFCA04.40102@wasp.net.au> (raw)
In-Reply-To: <200412150504.iBF54P912209@www.watkins-home.com>

Guy wrote:
> Maxtor drives....and no problems....You must be crazy!  :)
> 
> Well then, uh, it could...., humm....  That only leaves crazy!  :)
> 
> I give up!  You defended yourself well.  I have no idea.
> 

Note that it was not me who had the failing disk in the first place. I was just responding to the 
comment that 14 drives in a case sounded ludicrous. If the setup is reasonably well thought out and 
well cooled I see no issue. Yes, I do exceed my PSU continuous rating every time I spin up, but as I 
said I timed that overload at about 1.5 seconds and the PSU does not make any form of complaint.

I hope I'm more than just lucky with the Maxtor drives, but honestly I have had just as bad a run 
with every brand except Quantum (and who owns them now?). I figure by keeping the drives as cool as 
practical, in a stable environment with minimal temperature fluctuation and power cycling (this 
machine is a 24x7 server) then I'm probably fairly likely to get a better than average lifetime.

Sure with 29 Identical Maxtor drives I expect failures. I have a cold spare on standby just in case 
and the new 15 drive box will run Raid-6. In addition, this is a home entertainment system, it's not 
mission critical. Just a bit of fun on the weekends.

It's also a good test of the md and libata drivers. All up between the 29 drives I now have 7 
Promise SATA150TX4 controllers. Looking forward to hotswap :p)

-- 
Brad
                    /"\
Save the Forests   \ /     ASCII RIBBON CAMPAIGN
Burn a Greenie.     X      AGAINST HTML MAIL
                    / \

      reply	other threads:[~2004-12-15  5:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14  6:42 Busted disks caused healthy ones to fail comsatcat
2004-12-14  6:55 ` Guy
2004-12-14  8:28   ` comsatcat
2004-12-14 14:11     ` Michael Stumpf
2004-12-14 22:34       ` comsatcat
2004-12-14 15:22     ` Guy
2004-12-14 20:13       ` Brad Campbell
2004-12-14 21:47         ` Guy
2004-12-14 23:54           ` Alvin Oga
2004-12-15  1:03             ` Guy
2004-12-15  1:23               ` Alvin Oga
2004-12-14 21:49         ` Jim Paris
2004-12-14 22:13           ` Guy
2004-12-15  4:46           ` Brad Campbell
2004-12-15  5:04             ` Guy
2004-12-15  5:22               ` Brad Campbell [this message]

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=41BFCA04.40102@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=bugzilla@watkins-home.com \
    --cc=comsatcat@earthlink.net \
    --cc=jim@jtan.com \
    --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).