From: Neil Brown <neilb@suse.de>
To: Alberto Alonso <alberto@ggsys.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: When does a disk get flagged as bad?
Date: Thu, 31 May 2007 16:10:33 +1000 [thread overview]
Message-ID: <18014.26329.836246.525012@notabene.brown> (raw)
In-Reply-To: message from Alberto Alonso on Wednesday May 30
On Wednesday May 30, alberto@ggsys.net wrote:
>
> After thinking about your post, I guess I can see some logic behind
> not failing on the read, although I would say that after x amount of
> read failures a drive should be kicked out no matter what.
When md gets a read error, it collects the correct data from elsewhere
and tries to write it to the drive that apparently failed.
If that succeeds, it tries to read it back again. If that succeeds as
well, it assumes that the problem has been fixed. Otherwise it fails
the drive.
NeilBrown
next prev parent reply other threads:[~2007-05-31 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 4:16 When does a disk get flagged as bad? Alberto Alonso
2007-05-31 2:28 ` Mike Accetta
2007-05-31 2:49 ` Alberto Alonso
2007-05-31 6:10 ` Neil Brown [this message]
2007-06-02 0:07 ` Bill Davidsen
2007-06-02 15:50 ` Alberto Alonso
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=18014.26329.836246.525012@notabene.brown \
--to=neilb@suse.de \
--cc=alberto@ggsys.net \
--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).