All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaap Crezee <jaap@jcz.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Slow disks.
Date: Sat, 25 Dec 2010 19:12:02 +0100	[thread overview]
Message-ID: <4D1633F2.3040109@jcz.nl> (raw)
In-Reply-To: <alpine.DEB.1.10.1012251317420.27193@uplift.swm.pp.se>

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?

Jaap


  reply	other threads:[~2010-12-25 18:12 UTC|newest]

Thread overview: 41+ 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-24 11:40                         ` Rogier Wolff
2010-12-26 23:05                         ` Greg Freemyer
2010-12-27  0:27                           ` Rogier Wolff
2010-12-27  7:21                             ` Stan Hoeppner
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 [this message]
2010-12-25 21:28                 ` Michael Tokarev
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=4D1633F2.3040109@jcz.nl \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.