From: Maurice Hilarius <maurice@harddata.com>
To: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
Cc: linux-raid@vger.kernel.org, iusty@k1024.org
Subject: Re: mdadm and TLER (Time Limited Error Recovery)
Date: Tue, 08 Sep 2009 19:33:56 -0600 [thread overview]
Message-ID: <4AA70604.7020709@harddata.com> (raw)
In-Reply-To: <20090908184837.GA28217@teal.hq.k1024.org>
Iustin Pop wrote:
> ..
>> Anyways, clarification...
>> The only reason for TLER (Time Limited Error Recovery) is to behave
>> "friendly" toward RAID controllers that timeout disks.
>> In fact, md does not timeout disks as many Hardware RAID controllers do.
>> So, from md's point of view, TLER is useless, i.e. it has no benefit.
>>
>
> I'm sorry but I disagree here. *Especially* because md is used over
> normal SATA controllers most of the time, TLER is beneficial because the
> drive doesn't go catatonic for minutes at a time trying to recover a bad
> sector, which would (because md doesn't timeout disks) cause md to hung
> up the whole device. TLER will allow md to see the error quickly and
> attempt to rewrite (read) or retry/fail the disk (write) for a bad the
> sector.
>
> Just my understanding of the md stack.
>
> regards,
> iustin
>
>
I agree.
Before WD implemented this we would see cases quite often where a
perfectly good drive would get "kicked out"
of a RAID as frequently or even more often, than on a hardware RAID.
TLER management seems to have eliminated most of these cases.
--
Regards, Maurice
next prev parent reply other threads:[~2009-09-09 1:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 0:35 mdadm and TLER (Time Limited Error Recovery) Tim Rutter
2009-09-08 14:17 ` Mario 'BitKoenig' Holbe
2009-09-08 18:48 ` Iustin Pop
2009-09-08 19:45 ` Mario 'BitKoenig' Holbe
2009-09-09 1:33 ` Maurice Hilarius [this message]
2009-09-09 8:21 ` Simon Jackson
2009-09-09 9:00 ` Majed B.
2009-09-09 11:04 ` Mario 'BitKoenig' Holbe
2009-09-10 9:26 ` Simon Jackson
2009-09-10 9:39 ` Majed B.
2009-09-10 9:46 ` Robin Hill
2009-09-15 15:36 ` Simon Jackson
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=4AA70604.7020709@harddata.com \
--to=maurice@harddata.com \
--cc=Mario.Holbe@TU-Ilmenau.DE \
--cc=iusty@k1024.org \
--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).