From: Alberto Alonso <alberto@ggsys.net>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: When does a disk get flagged as bad?
Date: Sat, 02 Jun 2007 10:50:41 -0500 [thread overview]
Message-ID: <1180799441.20508.72.camel@w100> (raw)
In-Reply-To: <18014.26329.836246.525012@notabene.brown>
So, what kind of error is:
end_request: I/O error, dev sdb, sector 42644555
end_request: I/O error, dev sdb, sector 124365763
...
I am still trying to figure out why that just make one of my servers
unresponsive.
Is there a way to have the md code kick that drive out of the array?
The datacenter people are starting to get impatient having to reboot
it every other day.
Thanks,
Alberto
On Thu, 2007-05-31 at 16:10 +1000, Neil Brown wrote:
> 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
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Alberto Alonso Global Gate Systems LLC.
(512) 351-7233 http://www.ggsys.net
Hardware, consulting, sysadmin, monitoring and remote backups
prev parent reply other threads:[~2007-06-02 15:50 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
2007-06-02 0:07 ` Bill Davidsen
2007-06-02 15:50 ` Alberto Alonso [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=1180799441.20508.72.camel@w100 \
--to=alberto@ggsys.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).