From: Nebojsa Trpkovic <trx.lists@gmail.com>
To: st0ff@npl.de
Cc: "Stefan /*St0fF*/ Hübner" <stefan.huebner@stud.tu-ilmenau.de>,
linux-raid@vger.kernel.org
Subject: Re: TLER / CCTL timeout handling
Date: Thu, 25 Mar 2010 01:48:40 +0100 [thread overview]
Message-ID: <4BAAB2E8.2040104@gmail.com> (raw)
In-Reply-To: <4BAA8A21.8050601@stud.tu-ilmenau.de>
On 03/24/10 22:54, Stefan /*St0fF*/ Hübner wrote:
> Am 23.03.2010 23:10, schrieb Nebojsa Trpkovic:
>> Hello.
>>
>> I've found interesting text about TLER / CCTL
>> (http://en.wikipedia.org/wiki/Time-Limited_Error_Recovery )
>
> You might want to read on inside the ATA8-ACS, section about SCT Transport.
>>
>> on desktop class drives:
>> http://forums.storagereview.com/index.php/topic/28333-tler-cctl/
>>
>> So, the question is:
>>
>> If I make my drive report back it failed to read the requested sector,
>> how that report will be handeled?
>
> As far as I understood in recent answers to my questions: as expected.
>>
>> Will Linux software RAID be aware of that report and start some action
>> (rebuilding affected stripe or at least whole array, reallocating bad
>> sectors along the way) ?
>>
> Indeed. Michael Tokarev answered to me on 2/9/10:
> "On failed _read_ it tries to
> reconstruct data from other disk drives and writes the reconstructed
> data back to the drive where read failed. If the _write_ fails md will
> drop the disk."
>
> This means: if read fails and the drive does not report back, the
> following reconstructing write calls will fail, too. The disk gets
> dropped, because it (most probably) is still doing its error recovery on
> the former read request and by that not responding.
>
> If you enable ERC read timeouts, it'll report a media error (or
> something similar), but honour the write request. If you give the ERC
> write timeout a value that is not too small and also not too large (i.e.
> it shouldn't timeout the write-operation from the view of the kernel),
> it will either fix the pending sector, or reallocate it. If the ERC
> write timeout value is too small, it'll very aggressively reallocate
> sectors - which should not be the intention, as there are very few spare
> sectors (compared to the amount of sectors in total - only a few thousand).
>>
>> Thank you.
>> Nebojsa Trpkovic
>
> You're welcome, and all the best,
> Stefan
>
Thank you very much!
This is great answer (explaining a lot of things) and great news
(there's nothing to worry/hack about).
So, now we (desktop drives users) just have to wait for smartmontools
5.40 or pull source from SVN and set some reasonable ERC read timeouts.
Is value of 7 seconds considered as reasonable ERC read timeout?
Nebojsa
--
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
prev parent reply other threads:[~2010-03-25 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 22:10 TLER / CCTL timeout handling Nebojsa Trpkovic
2010-03-24 21:54 ` Stefan /*St0fF*/ Hübner
2010-03-25 0:48 ` Nebojsa Trpkovic [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=4BAAB2E8.2040104@gmail.com \
--to=trx.lists@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=st0ff@npl.de \
--cc=stefan.huebner@stud.tu-ilmenau.de \
/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).