From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: Resize on dirty array?
Date: Mon, 28 Aug 2006 08:36:01 +0200 [thread overview]
Message-ID: <ecu2sh$3nm$1@sea.gmane.org> (raw)
In-Reply-To: 17650.30521.355859.724575@cse.unsw.edu.au
Neil Brown <neilb@suse.de> wrote:
> I would be a lot happier about it if the block layer told me whether
> the fail was a Media error or some other sort of error.
This wouldn't help you either. I've seen drives (mainly Samsung) that
locked up the whole IDE bus after some simple (subsequent) sector-read-
errors.
And with strange IDE drivers (like PDC202XX_NEW) this could also
escalate to whole-machine freezes - I've also seen this and had to play
hardly with device-mapper's dm-error target to work around this :)
So IMHO at least the default behaviour should stay as it currently is:
if a drive fails, do never ever touch it again. Perhaps, you could make
such a "FAILING" feature somehow configurable (perhaps even on a
per-mirror base) in order to allow users to enable it for drives they
*do* know they don't show up such a bad behaviour.
regards
Mario
--
Independence Day: Fortunately, the alien computer operating system works just
fine with the laptop. This proves an important point which Apple enthusiasts
have known for years. While the evil empire of Microsoft may dominate the
computers of Earth people, more advanced life forms clearly prefer Macs.
prev parent reply other threads:[~2006-08-28 6:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 0:36 Resize on dirty array? James Peverill
2006-08-08 0:46 ` Neil Brown
2006-08-08 19:25 ` James Peverill
2006-08-09 4:09 ` Neil Brown
2006-08-09 11:28 ` James Peverill
2006-08-09 11:37 ` Martin Schröder
2006-08-09 13:05 ` Mark Hahn
2006-08-09 13:33 ` James Peverill
2006-08-09 21:17 ` David Greaves
2006-08-10 17:44 ` dean gaudet
2006-08-12 1:11 ` David Rees
[not found] ` <72dbd3150608111810m4e4a2e07r5ddcee2132dd6d9a@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0608111813250.29322@twinlark.arctic.org>
2006-08-12 2:05 ` David Rees
2006-08-12 4:36 ` Brad Campbell
2006-08-13 16:02 ` dean gaudet
2006-08-30 7:30 ` dean gaudet
2006-08-11 17:34 ` John Stoffel
2006-08-09 14:56 ` Henrik Holst
2006-08-12 7:22 ` Tuomas Leikola
2006-08-28 4:55 ` Neil Brown
2006-08-28 6:36 ` Mario 'BitKoenig' Holbe [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='ecu2sh$3nm$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).