Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Francois Barre" <francois.barre@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>,
	Christian Pernegger <pernegger@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: ICH7 sata-ahci + software raid warning
Date: Tue, 11 Jul 2006 14:33:59 +0200	[thread overview]
Message-ID: <fd8d0180607110533j7f9fe7c8k7ececea622d7c17b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607110823160.858@p34.internal.lan>

2006/7/11, Justin Piszcz <jpiszcz@lucidpixels.com>:
> Why not just --set-faulty or --fail with mdadm?
>

If you answer to "Bad blocks maybe, can't test that.", I'll say AFAIK,
--set-faulty will only stay at the md layer, and won't go through the
underlying driver (sata here, ata elsewhere, ...), so this will not
help diagnose the driver behaviour on block read problem.

If you answer to the fact that md does not mark the drive faulty, I
guess Christian was refering to an automatic to mark the disk faulty,
not a manual way, in order, for exemple, to trigger a resync with a
spare drive just after a drive failure has been detected (and not only
after the admin found it).

As an ugly workaround, a daemon script could look at the current drive
status regularly (in /sys, in /proc or trying to read /dev/sd?), and
mark the drive faulty on error...

  reply	other threads:[~2006-07-11 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 16:48 ICH7 sata-ahci + software raid warning Christian Pernegger
2006-07-11 12:23 ` Justin Piszcz
2006-07-11 12:33   ` Francois Barre [this message]
2006-07-11 12:40     ` Justin Piszcz
2006-07-11 12:47       ` Christian Pernegger
2006-07-11 12:44   ` Christian Pernegger

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=fd8d0180607110533j7f9fe7c8k7ececea622d7c17b@mail.gmail.com \
    --to=francois.barre@gmail.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=pernegger@gmail.com \
    /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