linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joachim Otahal <Jou@gmx.net>
To: Randy Terbush <randy@terbush.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID Class Drives`
Date: Thu, 18 Mar 2010 17:45:33 +0100	[thread overview]
Message-ID: <4BA258AD.5020605@gmx.net> (raw)
In-Reply-To: <7db987b31003170648j19e3346bi1050e703ef8c811c@mail.gmail.com>

Randy Terbush schrieb:
> So the question becomes, do I try it again with the replacement drives
> that Seagate is sending me, or do I hang them in my "desktop" and
> spend the money for RAID Class drives? (I've grown tired of this
> learning experience and would like to just have a dependable storage
> system)
>    
Desktop class drives are usually enough. On todays mobo's chipset SATA 
is enough too. You should take care of the temperature of the drives, 
30°C to 35°C is preferred, above 35°C the lifespan goes down, over 40°C 
rapidly down.
Do you have a regular checkarray interval? Like this one from debian 
(monthly first sunday):
57 0 * * 0 root [ -x /usr/share/mdadm/checkarray ] && [ $(date +\%d) -le 
7 ] && /usr/share/mdadm/checkarray --cron --all --quiet
Do you have a regular SMART check? Not only check the SMART status, keep 
the history of some values which change over time, most notably the 
Reallocated Sector Count, if that one changes every week on one drive 
(or even faster) it is time to take that drive out of the array.

> Why would these drives be developing errors as a result of their
> tortuous experience in a RAID array?
>    
I don't think RAID is more stress than normal use at home, it depends on 
how long they run, how often they spin up, how hot they get.
As for you description of the error behaviour: This is correct, 
RAID-SATA-drives don't spend a minute or more trying to read a possibly 
failing sector, most only try for less than 5 seconds to re-read a 
sector Also their mechanics have lower tolerance allowing higher MBTF 
values.

kind regards,

Joachim Otahal
--
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

  reply	other threads:[~2010-03-18 16:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 13:48 RAID Class Drives` Randy Terbush
2010-03-18 16:45 ` Joachim Otahal [this message]
2010-03-19  8:15   ` John Robinson
2010-03-19 16:43     ` Aryeh Gregor
2010-03-19 16:53       ` Mattias Wadenstein
2010-03-19 18:14       ` Joachim Otahal
2010-03-22  6:55       ` Leslie Rhorer
2010-03-22 16:29         ` Eric Shubert
2010-03-23  1:23           ` Brad Campbell
2010-03-23 17:45             ` Eric Shubert
2010-04-02  5:43               ` Leslie Rhorer
2010-04-02 20:04                 ` Richard Scobie
2010-04-05  2:50                   ` Leslie Rhorer
2010-03-19 17:53     ` Joachim Otahal
2010-03-20 17:26       ` Bill Davidsen
2010-03-21 16:14         ` Eric Shubert
2010-03-18 19:43 ` Randy Terbush
2010-04-18 12:11   ` CoolCold
     [not found]     ` <4BCB6484.7040500@stud.tu-ilmenau.de>
2010-04-19 10:11       ` CoolCold
     [not found]         ` <4BCC7C27.1000606@stud.tu-ilmenau.de>
2010-04-19 20:10           ` CoolCold

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=4BA258AD.5020605@gmx.net \
    --to=jou@gmx.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=randy@terbush.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).