From: Bill Davidsen <davidsen@tmr.com>
To: "Dean S. Messing" <deanm@sharplabs.com>
Cc: linux-raid@vger.kernel.org, brederlo@informatik.uni-tuebingen.de
Subject: Re: Help: very slow software RAID 5.
Date: Thu, 27 Sep 2007 18:17:45 -0400 [thread overview]
Message-ID: <46FC2C09.3010107@tmr.com> (raw)
In-Reply-To: <20070925181618.82F47102162@medulla.enet.sharplabs.com>
Dean S. Messing wrote:
> I have also discovered "smartctl" and have read that if the short smartctl
> tests are run daily and the long test weekly that the chances of being
> caught "with my pants down" are quite low, even in a two disk RAID-0
> config. What is your opinion?
>
There's a good paper on using smartctl to predict the health of disks,
and if you can't find it I probably have a copy somewhere, since I gave
a presentation on RAID issues which included it. But the basic premise
was that if you see errors of certain types, the drives are likely to
fail soon. It did *not* say that absent these warnings the drives were
unlikely to fail, un fact most drives which did fail did so without
warning. So for about 90% of the failures there is no warning.
I had servers a few years ago, running 6TB/server, on lots of small fast
drives, and I concluded that the predictive value of SMART was so small
that it didn't justify looking at the reports. Take that as my opinion,
assume that drives fail without warning.
I'm getting around to replying to several things you have said in
various posts, so that people who are threading answers will be happy...
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2007-09-27 22:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 23:09 Help: very slow software RAID 5 Dean S. Messing
2007-09-19 0:05 ` Justin Piszcz
2007-09-19 1:49 ` Dean S. Messing
2007-09-19 8:38 ` Justin Piszcz
2007-09-19 17:49 ` Dean S. Messing
2007-09-19 18:25 ` Justin Piszcz
2007-09-19 23:31 ` Dean S. Messing
2007-09-20 8:25 ` Justin Piszcz
2007-09-20 18:16 ` Michal Soltys
2007-09-20 19:06 ` Dean S. Messing
2007-09-20 15:33 ` Bill Davidsen
2007-09-20 18:47 ` Dean S. Messing
2007-09-20 21:08 ` Michael Tokarev
2007-09-21 0:58 ` Dean S. Messing
2007-09-21 13:00 ` Bill Davidsen
2007-09-21 20:01 ` Dean S. Messing
2007-09-21 20:21 ` Dean S. Messing
2007-09-25 9:31 ` Goswin von Brederlow
2007-09-25 18:16 ` Dean S. Messing
2007-09-25 21:46 ` Goswin von Brederlow
2007-09-25 23:50 ` Dean S. Messing
2007-09-26 1:45 ` Goswin von Brederlow
2007-09-27 6:23 ` Dean S. Messing
2007-09-27 9:51 ` Michal Soltys
2007-09-27 22:10 ` Backups w/ rsync (was: Help: very slow software RAID 5.) Dean S. Messing
2007-09-28 7:57 ` Backups w/ rsync Michael Tokarev
2007-09-28 10:23 ` Goswin von Brederlow
2007-09-28 11:18 ` Michal Soltys
2007-09-28 12:47 ` Goswin von Brederlow
2007-09-28 14:17 ` Michal Soltys
2007-09-29 0:11 ` Dean S. Messing
2007-09-29 8:43 ` Michael Tokarev
2007-09-28 14:48 ` Bill Davidsen
2007-09-28 14:57 ` Wolfgang Denk
2007-09-28 16:50 ` Bill Davidsen
2007-10-01 4:45 ` Michal Soltys
2007-09-28 15:11 ` Jon Nelson
2007-09-28 16:25 ` Bill Davidsen
2007-09-28 16:52 ` Jon Nelson
2007-09-27 22:40 ` Help: very slow software RAID 5 Bill Davidsen
2007-09-28 23:38 ` Dean S. Messing
2007-09-29 14:52 ` Bill Davidsen
2007-09-27 22:17 ` Bill Davidsen [this message]
2007-09-28 23:21 ` Dean S. Messing
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=46FC2C09.3010107@tmr.com \
--to=davidsen@tmr.com \
--cc=brederlo@informatik.uni-tuebingen.de \
--cc=deanm@sharplabs.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).