From: CoolCold <coolthecold@gmail.com>
To: st0ff@npl.de
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID Class Drives`
Date: Mon, 19 Apr 2010 14:11:59 +0400 [thread overview]
Message-ID: <h2rf19d625d1004190311qefcc12f3q599acd47d8732046@mail.gmail.com> (raw)
In-Reply-To: <4BCB6484.7040500@stud.tu-ilmenau.de>
On Sun, Apr 18, 2010 at 11:59 PM, Stefan /*St0fF*/ Hübner
<stefan.huebner@stud.tu-ilmenau.de> wrote:
> Hi!
>
> Am 18.04.2010 14:11, schrieb CoolCold:
>> I don't really understand one point - why it failed? Did the
>> controller dropped device because it wasn't responsible or md did
>> this? Rephrasing my question - this is really "tuning" for controller
>> not to drop device and report error or for md?
>
> If a desktop class drive starts its error recovery, it becomes
> unresponsive. MD thinks this, but it isn't smart. It tries to rewrite
> the sector while the drive itself is still in error recovery mode and by
> that unresponsive. The write fails, MD drops the device.
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?
Even if drive doens't become irresponsible and returns "error on
write" it will be dropped anyway.
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.
>
>> And if drive has errors anyway, why it shouldn't be dropped, is it for
>> just in case we have read error, we can try to rewrite it from the
>> alive array part? If we have write error, we gonna drop drive from
>> array anyway..
>>
> Because that is the reason hdd manufacturers built in spare sectors and
> internal error recovery procedures. Think about the write density of
> todays drives, think about the many influences which it must work with.
> The nearly atomically-sized bits on the platter.
> IT IS NOT POSSIBLE to build a perfect drive on todays specifications.
> That's why this exists in the first place. And as we can see it is a
> very easy way for hdd manufacturers to make extra money. Just label
> those drives that also passed the very last quality test (not only the
> other 10 tests before) "superdrive", sell them for nearly double the
> price and give them a firmware, where the advanced features are just
> enabled as default...
>
> /stefan
>
>
--
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
next prev parent reply other threads:[~2010-04-19 10:11 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 [this message]
[not found] ` <4BCC7C27.1000606@stud.tu-ilmenau.de>
2010-04-19 20:10 ` CoolCold
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=h2rf19d625d1004190311qefcc12f3q599acd47d8732046@mail.gmail.com \
--to=coolthecold@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=st0ff@npl.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).