From: CoolCold <coolthecold@gmail.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID Class Drives`
Date: Tue, 20 Apr 2010 00:10:31 +0400 [thread overview]
Message-ID: <o2vf19d625d1004191310r9d1e3337jd48d2376f2df3c15@mail.gmail.com> (raw)
In-Reply-To: <4BCC7C27.1000606@stud.tu-ilmenau.de>
On Mon, Apr 19, 2010 at 7:52 PM, Stefan /*St0fF*/ Hübner
<stefan.huebner@stud.tu-ilmenau.de> wrote:
> Hi again!
>
> Am 19.04.2010 12:11, schrieb CoolCold:
>> Stop-stop. It is clear that timeouting "read" request in short period
>> is good idea, but i wanna know about writes
>> Does write fail because controller returns smth like "media error" or
>> md has internal operation timeouts?
>
> Afaik the kernel has internal timeouts, that make unresponsive disks
> drop out.
>
>> Even if drive doens't become irresponsible and returns "error on
>> write" it will be dropped anyway.
>
> I'm not sure, you might be right.
>>
>> So, SCT-ERC setting will prevent drive to be irresponsible for long
>> time which may be desirable in case of:
>> a) md doesn't have it's own timeouting mechanism and the whole md
>> device will be stucked
>> b) drive ( another partition ) is part of another array/lvm
>> pv/whatever and that device will be stucked too.
>>
>
> Nope. In the ATA8-ACS it is noted about like that: if the erc timer is
> about to expire, it is the duty of the drive to reallocate the sector
> and save the data-to-write onto the spare sector.
>
> So actually, if a write error occurs the drive should never report it as
> long as spare sectors are available. That's because of ncq/tcq and scsi
> taskfiles - which make it nearly impossible to find out which write
> command failed and reconstruct the data for a retry. On the other hand:
> the drive should still know the data somehow ;)
>
> The same applies to non-enabled write-erc. The drive only runs the
> whole error-correction before it reallocates the sector (I had this 14
> times already (according to SMART) on my laptop - weird if it doesn't
> respond for 2min, but then all of a sudden everything's great again).
>
> All the best and I hope I could help at least a bit,
> Stefan
>
Thanks a lot!
After some additional googling, i've found similar dialogue on this
list - http://kerneltrap.org/mailarchive/linux-raid/2010/3/25/6883733
. It's contents and links cleared almost anything for me.
1) ERC ( TLER / CCTL ) is primary aimed on read requests.
2) Should help on writes because "if the erc timer is about to expire,
it is the duty of the drive to reallocate the sector and save the
data-to-write onto the spare sector"
Accoring to this statements, if md kicked out drive with ERC enabled,
drive is almost dead. Is it true in practice?;)
--
Best regards,
[COOLCOLD-RIPN]
--
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-04-19 20:10 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
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 [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=o2vf19d625d1004191310r9d1e3337jd48d2376f2df3c15@mail.gmail.com \
--to=coolthecold@gmail.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).