From: Michael Tokarev <mjt@tls.msk.ru>
To: Jaap Crezee <jaap@jcz.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Slow disks.
Date: Sun, 26 Dec 2010 00:28:37 +0300 [thread overview]
Message-ID: <4D166205.4070205@msgid.tls.msk.ru> (raw)
In-Reply-To: <4D1633F2.3040109@jcz.nl>
25.12.2010 21:12, Jaap Crezee wrote:
> On 12/25/10 13:19, Mikael Abrahamsson wrote:
>> On Sat, 25 Dec 2010, Rogier Wolff wrote:
>> Read errors will use parity drive and be re-written by the md layer.
>
> Can you show us *that* code? I don't recall seeing this behaviour....
> Just one read error and "bang". Or does the kernel not report the first
> few read errors and just continues without telling us?
> I don't like that. With a normal disk without raid I would have had some
> log telling me the disk got bad?
The code is in the md driver.
This behavour is here for several years. If the drive respond in time
ofcourse - if it tries to re-read the problematic sector forever and
ignores other commands during this time it will be kicked off any
array - be it software or hardware.
The logs will be in whatever logfile your kernel messages are logged to.
And yes, the application which reads the "problematic" area is _not_
notfied, since the data gets restored from other driver - if that was
an md array with sufficient redundancy (any non-degraded raid other
than raid0).
/mjt
next prev parent reply other threads:[~2010-12-25 21:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 14:15 Slow disks Rogier Wolff
2010-12-20 18:06 ` Bruno Prémont
2010-12-20 18:32 ` Greg Freemyer
2010-12-22 10:43 ` Rogier Wolff
2010-12-22 15:59 ` Greg Freemyer
2010-12-22 16:27 ` Jeff Moyer
2010-12-22 22:44 ` Rogier Wolff
2010-12-23 14:40 ` Jeff Moyer
2010-12-23 17:01 ` Rogier Wolff
2010-12-23 17:47 ` Jeff Moyer
2010-12-23 18:51 ` Greg Freemyer
2010-12-23 19:10 ` Jaap Crezee
2010-12-23 22:09 ` Greg Freemyer
2010-12-24 11:40 ` Rogier Wolff
2010-12-26 23:05 ` Greg Freemyer
2010-12-27 0:27 ` Rogier Wolff
2010-12-24 10:45 ` Rogier Wolff
2010-12-23 17:05 ` Jaap Crezee
2010-12-26 23:38 ` Mark Knecht
2010-12-27 0:34 ` Rogier Wolff
2010-12-27 3:12 ` Mark Knecht
2010-12-27 18:20 ` Krzysztof Halasa
2010-12-24 13:01 ` Krzysztof Halasa
2010-12-24 15:24 ` Michael Tokarev
2010-12-24 20:58 ` Krzysztof Halasa
2010-12-25 12:14 ` Rogier Wolff
2010-12-25 12:19 ` Mikael Abrahamsson
2010-12-25 18:12 ` Jaap Crezee
2010-12-25 21:28 ` Michael Tokarev [this message]
2010-12-26 21:40 ` Rogier Wolff
2010-12-26 23:17 ` Greg Freemyer
2010-12-26 23:49 ` Rogier Wolff
2010-12-26 22:07 ` Niels
2010-12-27 10:56 ` Tejun Heo
2010-12-20 19:09 ` Jeff Moyer
2010-12-22 20:52 ` David Rees
2010-12-22 22:46 ` Rogier Wolff
2010-12-22 23:13 ` David Rees
[not found] <fa.C+PyZdFdHUxRFDJDF3KlrfaJASk@ifi.uio.no>
2010-12-21 12:29 ` Arto Jantunen
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=4D166205.4070205@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=jaap@jcz.nl \
--cc=linux-kernel@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