From: "majianpeng" <majianpeng@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: About raid5 read error handle when raid5 was degraded.
Date: Mon, 21 May 2012 18:47:58 +0800 [thread overview]
Message-ID: <201205211847549688311@gmail.com> (raw)
Hi all:
I readed the latest code in function :
raid5_end_read_request():
>> else if (conf->mddev->degraded >= conf->max_degraded)
>> printk_ratelimited(
>> KERN_WARNING
>> "md/raid:%s: read error not correctable "
>> "(sector %llu on %s).\n",
>> mdname(conf->mddev),
>> (unsigned long long)(sh->sector
>> + rdev->data_offset),
>> bdn);
If this occur,then exec md_error().In md_error(), remove this disk.
The raid5 will fail and lost all data.
Why do call rdev_set_badsector() for this situation?
Thanks!
--------------
majianpeng
2012-05-21
next reply other threads:[~2012-05-21 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 10:47 majianpeng [this message]
2012-05-21 22:36 ` About raid5 read error handle when raid5 was degraded NeilBrown
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=201205211847549688311@gmail.com \
--to=majianpeng@gmail.com \
--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).