From: Stan Hoeppner <stan@hardwarefreak.com>
To: Marcus Sorensen <shadowsor@gmail.com>
Cc: Phil Turmel <philip@turmel.org>,
Daniel Pocock <daniel@pocock.com.au>,
linux-raid@vger.kernel.org
Subject: Re: md RAID with enterprise-class SATA or SAS drives
Date: Thu, 10 May 2012 16:43:10 -0500 [thread overview]
Message-ID: <4FAC366E.7080309@hardwarefreak.com> (raw)
In-Reply-To: <CALFpzo6BECrv2eTbSRKwUzpTopx_0EmD+UipqUf-XE=vzz2OnQ@mail.gmail.com>
On 5/10/2012 10:26 AM, Marcus Sorensen wrote:
> * Using smartctl to increase the ERC timeout on enterprise SATA
> drives, say to 25 seconds, for use with md. I have no idea if this
> will cause the drive to actually try different methods of recovery,
> but it could be a good middle ground.
If a drive needs 25 seconds to recover from a read error it should have
been replaced long ago.
The only thing that increasing these timeouts to silly high numbers does
is, hopefully for those doing it anyway, prolong the replacement
interval of failing drives.
Can anyone guess what the big bear trap is that this places before you?
The rest of the drives in the array have been held over much longer as
well. So when you go to finally rebuild the replacement for this 25s
delay king, you'll be more likely to run into unrecoverable errors on
other array members. Then you chance losing your entire array, and, for
many here, all of your data, as hobbyists don't do backups. ;)
Fist 2 rules of managing RAID systems:
1. Monitor drives and preemptively replace those going down hill BEFORE
your RAID controllers or md raid kick them
1a. Don't wait for controllers/md raid to kick bad drives
2. Data is always worth more than disks drives
2a. If drives cost more than your lost data, you're doing it wrong
--
Stan
next prev parent reply other threads:[~2012-05-10 21:43 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 22:00 md RAID with enterprise-class SATA or SAS drives Daniel Pocock
2012-05-09 22:33 ` Marcus Sorensen
2012-05-10 13:34 ` Daniel Pocock
2012-05-10 13:51 ` Phil Turmel
2012-05-10 14:59 ` Daniel Pocock
2012-05-10 15:15 ` Phil Turmel
2012-05-10 15:26 ` Marcus Sorensen
2012-05-10 16:04 ` Phil Turmel
2012-05-10 17:53 ` Keith Keller
2012-05-10 18:10 ` Mathias Burén
2012-05-10 18:23 ` Phil Turmel
2012-05-10 19:15 ` Keith Keller
2012-05-10 18:42 ` Daniel Pocock
2012-05-10 19:09 ` Phil Turmel
2012-05-10 20:30 ` Daniel Pocock
2012-05-11 6:50 ` Michael Tokarev
2012-05-21 14:19 ` Brian Candler
2012-05-21 14:29 ` Phil Turmel
2012-05-26 21:58 ` Stefan *St0fF* Huebner
2012-05-10 21:43 ` Stan Hoeppner [this message]
2012-05-10 23:00 ` Marcus Sorensen
2012-05-10 21:15 ` Stan Hoeppner
2012-05-10 21:31 ` Daniel Pocock
2012-05-11 1:53 ` Stan Hoeppner
2012-05-11 8:31 ` Daniel Pocock
2012-05-11 13:54 ` Pierre Beck
2012-05-10 21:41 ` Phil Turmel
2012-05-10 22:27 ` David Brown
2012-05-10 22:37 ` Daniel Pocock
[not found] ` <CABYL=ToORULrdhBVQk0K8zQqFYkOomY-wgG7PpnJnzP9u7iBnA@mail.gmail.com>
2012-05-11 7:10 ` David Brown
2012-05-11 8:16 ` Daniel Pocock
2012-05-11 22:28 ` Stan Hoeppner
2012-05-21 15:20 ` CoolCold
2012-05-21 18:51 ` Stan Hoeppner
2012-05-21 18:54 ` Roberto Spadim
2012-05-21 19:05 ` Stan Hoeppner
2012-05-21 19:38 ` Roberto Spadim
2012-05-21 23:34 ` NeilBrown
2012-05-22 6:36 ` Stan Hoeppner
2012-05-22 7:29 ` David Brown
2012-05-23 13:14 ` Stan Hoeppner
2012-05-23 13:27 ` Roberto Spadim
2012-05-23 19:49 ` David Brown
2012-05-23 23:46 ` Stan Hoeppner
2012-05-24 1:18 ` Stan Hoeppner
2012-05-24 2:08 ` NeilBrown
2012-05-24 6:16 ` Stan Hoeppner
2012-05-24 2:10 ` NeilBrown
2012-05-24 2:55 ` Roberto Spadim
2012-05-11 22:17 ` Stan Hoeppner
-- strict thread matches above, loose matches on Subject: below --
2012-05-10 1:29 Richard Scobie
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=4FAC366E.7080309@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=daniel@pocock.com.au \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
--cc=shadowsor@gmail.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 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).