linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: [PATCH] proactive raid5 disk replacement for 2.6.11
Date: Mon, 15 Aug 2005 13:29:35 +0200	[thread overview]
Message-ID: <ddpuau$nv8$1@sea.gmane.org> (raw)
In-Reply-To: 1124050204.3810.28.camel@localhost.localdomain

Hi,

Pallai Roland <dap@mail.index.hu> wrote:
>  this is a feature patch that implements 'proactive raid5 disk
> replacement' (http://www.arctic.org/~dean/raid-wishlist.html),
> that could help a lot on large raid5 arrays built from cheap sata
...
>  linux software raid is very fragile by default, the typical (nervous)

I just had a fast look over your patch, so please forgive me if I could
have found the answer in the code.
What I'm wondering about is how does your patch make the whole system
behave in case of more harmful errors?
The read errors you are talking about are quite harmless regarding
subsequent access to the device. Unfortunately there *are* errors (even
read errors, too), especially when you are talking about cheap IDE (ATA,
SATA) equipment, where subsequent access to the device results in
infinite (bus-)lockups. I think, this is the reason why Software-RAID
does never ever touch a failing drive again. If you are changing this
behaviour in general, you risk lock-ups of the raid-device just because
one of the drives got locked up.
What I did not find in your patch is some differentiation between the
harmless and harmful error conditions. I'm not even sure, if this is
possible at all.

regards
   Mario
-- 
Um mit einem Mann gluecklich zu werden, muss man ihn sehr gut
verstehen und ihn ein bisschen lieben.
Um mit einer Frau gluecklich zu werden, muss man sie sehr lieben
und darf erst gar nicht versuchen, sie zu verstehen.


  parent reply	other threads:[~2005-08-15 11:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 20:10 [PATCH] proactive raid5 disk replacement for 2.6.11 Pallai Roland
2005-08-14 21:29 ` [PATCH] proactive raid5 disk replacement for 2.6.11 [fixed patch] Pallai Roland
2005-08-15  6:45 ` [PATCH] proactive raid5 disk replacement for 2.6.11 Claas Hilbrecht
2005-08-15 11:29 ` Mario 'BitKoenig' Holbe [this message]
2005-08-15 13:50   ` Pallai Roland
     [not found] ` <C0A1E607B5206F88D89CAF42@192.168.1.22>
2005-08-22 10:47   ` Molle Bestefich
2005-08-22 11:56     ` Pallai Roland
2005-08-22 13:55       ` Molle Bestefich
2005-08-28 23:35         ` Neil Brown

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='ddpuau$nv8$1@sea.gmane.org' \
    --to=mario.holbe@tu-ilmenau.de \
    --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).